Table of Contents
Advertisement
Location of Optional APIs and Web Messaging Service
The default authentication Web services are located in the /Motorola/UCA/Client/Authentication and the
/Motorola/UCA/ServerManagement/Authentication directories under IIS. During the UCA login processes, these
Web services are called to authenticate the user's credentials against the user data found in the UCA database.
The system can be configured to call a custom authentication Web service that authenticates against an entirely
different database, if needed.
The server management and maintenance Web services are located in the /Motorola/UCA/ServerManagement/
directory under IIS. These Web services can be used to populate the UCA server database with key information,
such as device users, phone extensions, etc. External programs can be developed that utilize the functionality
found in these Web services as an alternative or in addition to using the UCA server Web Console in some cases.
For example, if a customer finds over time that they need more CA50s in a given department (e.g., Lumber) these
new devices most likely need phone extensions. If the number of CA50s in Lumber exceeds the number of phone
extensions that were allocated to the Lumber group in the UCA server, more phone extensions need to be
assigned to Lumber. The assignment of these new phone extensions to the Lumber group in the UCA server
database can be accomplished by using the Web Console phone extension GUI functionality, or by creating an
external program that uses the AddExtension() function found in the Phone Extension Management Web service.
The messaging Web services are located in the /Motorola/UCA/ServerManagement directory under IIS. This Web
service can be used by external programs to send asynchronous messages to logged on CA50 users.
Alternate Mechanism for Login and Authentication
Device user authentication is based on the user information on the UCA server. Alternatively, customers with an
existing database that contains user (staff) information can use their existing user authentication mechanism. Note
that the customer's authentication process is used only for authentication purposes; other user information must be
stored in the UCA database, such as the user's group and role.
In this case, the customer can use a Web service with the same signature as that of the UCA Authentication web
service, and include this in the web.config. See
updating web config.
c:/Inetpub/wwwroot/Motorola/UCA/Client\web.config
<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>
Similarly, if a customer's database contains the console users' (typically administrators') information, the customer
must provide an alternative web service similar to the one UCA uses for console user authentication in order to use
this for console user authentication. To do this, the customer must change the URL in the web.config to point to his
own Web service. See
Web config.
C:\Inetpub\wwwroot\Motorola\UCA\UCAConsole\web.config
<applicationSettings>
<UCACommon.Properties.Settings>
<setting name=" UCACommon_ConsoleAuthService_ManagementAuthentication" serializeAs="String">
<value>http://localhost/Motorola/UCA/ServerManagement/Authentication/
ManagementAuthentication.asmx </value>
</setting>
</UCACommon.Properties.Settings>
</applicationSettings>
Customizing the Process Flow on page 11-6
Customizing the Console Login Process on page 11-43
UCA Server Optional APIs 11 - 3
for information on
for more information on updating
Advertisement
Table of Contents
Troubleshooting
