11 - 6 CA50/UCA Client & Server Developer & User Guide
Example 3 - Authentication Requires Additional Information, Process Continues
authenticated = false
continueOn = true
token (string) = "GetUserID"
Return values in this example indicate that the UCA Authentication Process is not over. The token string
“GetUserID” represents the next step in the UCA Authentication Process. This token is used to look up a URL
in the UCA DB System Settings. The token string appends to "System.Login.Token." and the resulting string is
looked up in the S_SystemVariables table for a reference to the B_SystemSettings table (svID). The svID is
looked up in the B_SystemSettings to get the URL.
The DeviceRegistration Web Service returns the URL to the device to which it browses. In the default DB
configuration, the token maps to "GetUser.aspx." The code behind GetUser.aspx calls the AuthenticateUser
method, also in the Authentication Web Service. The return values from AuthenticateUser are utilized in the
same manner as the response from AuthenticateMAC described above. The return values indicate whether or
not the process is complete and if not report the next step. This process can continue to collect a password, a
group (department), etc. from the user during login. This process is configurable.
When the device or user is finally validated, a user profile is generated and embedded in a Web page or
returned to the device in response to the DeviceRegistration Web Service call. See
for a diagram of the UCA Authentication Process.
Customizing the Process Flow
The default UCA Authentication Web Service used in the UCA Authentication Process can be replaced by an
Authentication Web Service written by a customer or integrator.
This can be accomplished as follows:
1.
Create an Authentication Web Service that matches the signature, methods and return values of the UCA
Authentication Web Service.
2.
Change the Web.config Web reference to point to the new Authentication Web Service.
3.
Modify the system settings login tokens to point to the new aspx pages.
Motorola provides an example Authentication Web Service with method stubs that can be used as a starting point
for a customer or integrator who wishes create their own.
To change the Web.config to use a different Authentication Web Service, find the following section in the
Web.config file:
<applicationSettings>
<UCACommon.Properties.Settings>
<setting name="UCACommon_localhost_Authentication" serializeAs="String">
<value>http://localhost/Motorola/UCA/Client/Authentication/Authentication.asmx</value>
</setting>
</UCACommon.Properties.Settings>
</applicationSettings>
In the default installation, Web.config is located in: c:/Inetpub/wwwroot/Motorola/UCA/Client.
Change the <value> tag above to point to the new Authentication Web Service and the UCA server calls the new
Authentication Web Service during the UCA Authentication Process. This setting may be encrypted for security
purposes. See
UCA Server Security on page 6-54
for more information.
Summary of Contents for CA50
Page 1: ...CA50 UCA Client Server Developer User Guide ...
Page 2: ......
Page 3: ...CA50 UCA Client Server Developer User Guide 72E 93914 02 Revision A November 2009 ...
Page 18: ...xvi CA50 UCA Client Server Developer User Guide ...
Page 24: ...xxii CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 30: ...1 6 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 34: ...2 4 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 48: ...3 14 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 106: ...4 58 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 109: ...UCA Client Application on the CA50 5 3 Page intentionally blank ...
Page 110: ...5 4 CA50 UCA Client Server Developer User Guide ...
Page 135: ...UCA Server 6 25 Figure 6 30 Installing Prerequisites Figure 6 31 SQL Server Setup ...
Page 200: ...7 32 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 284: ...9 56 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 302: ...10 18 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 350: ...11 48 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 358: ...12 8 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 418: ...A 6 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 436: ...B 18 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 478: ...E 12 CA50 UCA Client Server Developer User Guide 6 7 8 9 10 11 ...
Page 488: ...F 4 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 492: ...G 4 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 510: ...I 14 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 538: ...Index 12 CA50 UCA Client Server Developer User Guide ...
Page 540: ......
Page 541: ......