An application developer is attempting to implement device single sign-on (SSO) as specified in the following example:
<securityTests>
<mobileSecurityTest name="FormTest">
<testDeviceID provisioningType="none"/>
<testUser realm="SampleAppRealm"/>
</mobileSecurityTest>
</securityTests>
<realms>
<realm name="SampleAppRealm" loginModule="MyLoginModule">
<className>com.worklight.core.auth.ext.FormBasedAuthenticator</className>
</realm>
</realms>
<loginModules>
<loginModule name="MyLoginModule" ssoDeviceLoginModule="WLDeviceAutoProvisioningLoginModule"> className>com.worklight.core.auth.exp.NonValidatingLoginModule</className>
</loginModule>
</loginModules>
Upon testing the configuration, the developer finds unexpected results, such as the Worklight project failing to start.
What does the application developer need to do to bring the SSO configuration to a consistent state?
A. Set the sso.cleanup.taskFrequencyInSeconds server property.
B. Specify <testUser realm="SampleAppRealm" sso="true"/> in the mobile security test.
C. Add the following line to the mobile security test <test realm="MySSO" isInternalUserID=:true"/>
D. Add the following line to the WMAppManifest.xml file: <Capability Name=’ID_CAP_IDENTITY_DEVICE’ />
|
Download Printable PDF. VALID exam to help you PASS. |
 |