In the varied environments where the Profile Manager solution is installed, there may be an existing launcher application running on the device. This provides the customer with the ability to keep their existing launcher for the user sign-on process and then pass the user information to the Profile Client to authenticate with the Profile Manager.
The four tags used in this environment are:
Key_user_name
Key_user_pwd
Key_submit
Key_domain
The values entered in these tags identify the input fields to automate the login process. As an illustration, shown below is the actual html of a sample login screen:
<div class="input-row">
<table>
<tr>
<td>
<p> <label style="margin-top:-14px" for="username">Login ID:</label></p>
</td>
<td>
<span class="ctrl">
<input type="text" name="username" id="username" class="textinput" value=""/>
</span>
</td>
</tr>
</table>
</div>
<div class="input-row">
<table>
<tr>
<td>
<p> <label style="margin-top:-14px" for="password">Password:</label></p>
</td>
<td>
<span class="ctrl">
<input type="password" name="password" id="password" class="textinput"autocomplete="off"/>
</span>
</td>
</tr>
</table>
</div>
<div class="button-row">
<span class="ctrl">
<input type="submit" value="Login" id="submit" class="formButton"
onclick="this.disabled=true;document.body.style.cursor = 'wait';
this.className='formButton-disabled';form.submit();return false;"/>
The highlighted fields in the HTML example are the content of the login screen sent to the mobile device from the customer’s authentication system. Once authenticated, the Profile Client receives the credentials through an intent from the third-party launcher application and passes the credentials to the appropriate tagged fields. The Profile Client receives the input from the launcher by intent, and then provides the input to the User ID = id="username", and Password = id=”password” entries. These fields are sent back to the authorizing system with id=”submit”.
By correctly identifying the html entry ID Fields, the third-party application can pass the credentials to the Profile Client to log in with the credentials passed to the Client.
In this example, the three tags are populated with:
Key_user_name: “username”
Key_user_pwd: “password”
Key_submit: “submit”
The domain prefix is not shown in this example.
