Home Learn More Purchase Knowledge Base Support Contact

Search:     Advanced search

Remote Authentication scenarios

Article ID: 184
Last updated: 02 Mar, 2008
Add comment
Views: 650
Comments: 0
Here are some examples/scenarios for Remote Authentication:
  1. On the first authentication request the remote user is added to KBPublisher table of users.
    On the second and subsequent requests he/she is authenticated by KBPublisher's built in authentication.
    KB_AUTH_LOCAL = 1
    KB_AUTH_TYPE = 1
    KB_AUTH_REFRESH_TIME = 1.

  2. Always authenticate by Remote Authentication and rewrite user data in the knowledgebase.
    KB_AUTH_LOCAL = 0
    KB_AUTH_TYPE = 1
    KB_AUTH_REFRESH_TIME = 1

  3. On the first authentication request the remote user is added to KBPublisher users.
    On the second and subsequent requests the user is authenticated by remote authentication and his/her KBPublisher data is synchronized with data provided by your script, depending on the KB_AUTH_REFRESH_TIME.
    KB_AUTH_LOCAL = 0
    KB_AUTH_TYPE = 1
    KB_AUTH_REFRESH_TIME = 3600*24*30 (30 days).

  4. KBPublisher tries to authenticate the user by built-in Authentication first.On failure KBPublisher tries to authenticate the user by Remote Authentication.
    KB_AUTH_LOCAL = 1
    KB_AUTH_TYPE = 2

  5. If user IP matches KB_AUTH_LOCAL_IP range, then KBPublisher tries to authenticate the user by built-in Authentication first. If the IP does not match,or built-in authentication fails, KBPublisher tries to authenticate the user by Remote Authentication.
    KB_AUTH_LOCAL = 1
    KB_AUTH_LOCAL_IP = '192.168.1.1-192.168.255.255';
    KB_AUTH_TYPE = 2
This article was:   Helpful | Not Helpful Add comment
Prev   Next
Different ways for Remote Authentication     Knowledgebase

RSS

© 2008 Double Jade LLC | customer.service@kbpublisher.com