Remote Authentication scenarios

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

Adding KB_AUTH_AUTO = 1 to any of these means the user will not be asked to type in their username and password.
System will get that information automatically. See this article how to set up Auto Authentication.