NFIS Access

NFIS Access provides users capabilities to create Public accounts which users can then authenticate through the "Public" jurisdiction. Many NFIS Web applications have requirements for user contact information, NFIS Access allows for the maintenance of profile information for these applications. NFIS Access allows applications to retrieve profile and role information. All the software components of NFIS Access have been created in-house by the NFIS software development team.

Current Features

1. Provides a Web interface for Single Sign On (SSO) to the NFIS network.
2. Provides a Web interface allowing users who do not belong to a NFIS authenticating jurisdiction to create a user account.
   1. Users who do not have a "home" jurisdiction are able to register for "Public" - a local jurisdiction. User credentials (username, password, jurisdiction name, etc.) for local jurisdictions are maintained by NFIS.
   2. Users who belong to a remote jurisdiction (can provide authentication services via DACS) do not need to create an account.
3. Provides ability to add/modify profile information associated with an existing account.
   1. Users are authenticated via DACS prior to supplying profile information.
   2. All profile information is maintained by NFIS, and cannot be stored nor retrieved using DACS.
   3. Email confirmations are sent for all profile additions and modifications.
4. All language components used in the Web interface can be viewed in both English and French.
5. Provides core dacs_local_auth services for both the "Public" and "NRCan" jurisdictions. As DACS only provides a framework for authentication, and does not actually authenticate users - these services are essential for NFIS operations.
6. Provides three essential Web services which are integral components for the software used by the National Forestry Database Program (NFDP) and National Afforestation Inventory (NAI). All three services require a user to register his/her profile with NFIS (that is, being able to authenticate with DACS is not sufficient).
   1. AccountID Service - When forwarded a DACS cookie, the Account ID Service will return an XML reply with the user's account id if the user has also has associated profile information.
   2. UserProfile Service - Returns an XML reply containing a user's profile information.
   3. ApplicationRoles Service - Returns an XML reply of roles for a specific user and application name.