Customising login and database authentication

The Community Portal has two main methods of allowing authentication:

• Windows/Trusted IIS authentication
• database authentication.

Also see Security settings.

Trusted authentication

Trusted authentication can be from active directory or Novell if integrating with e-directory. The IIS user name can then be validated against the user's:

• Community ID
• Network Login Name (on the Other tab in Community Maintenance).

See Single sign on authentication settings.

To allow community member accounts to use trusted authentication:

1. Set the IIS server to use trusted authentication. See IIS server registry settings.
2. Open the Other tab of Community Maintenance.

   

3. Click to add a network login name and password to allow the community member to access the portal. See Managing Community Portal accounts.
4. Click to import network login information from a file.

Database authentication

This stores the user login name and password inside the Synergetic database. The passwords are encrypted within the database.

• The login can be:
  • shared by the spouse of the community member
  • unique to the person.
• These logins can be loaded in bulk using a comma delimited text file of the form:
  • ID,Password,Joint indicator (J).

  For example: 1001,Pa$$w0rd,J

See Creating community portal accounts in a batch.

To allow community member accounts to use database authentication, set the IIS server to use database authentication. See IIS server registry settings.

You can also configure the Community Portal to run multiple databases at once. See Running the community portal against multiple database servers.

Last modified: 15/10/2013 4:08:15 PM