workflowMessages.properties revision 41ca2ff36bd32cf47bde21a61199a78df0618e16
5061N/A# $Id: workflowMessages.properties,v 1.20 2010/01/04 19:10:50 veiming Exp $
3853N/Aajax.user.privilege.invalid=User does not have privileges to perform this task.
3853N/Afile.upload.size.limit.exceeded=Size limit Exceeded. Please verify your metadata file and try again.
3853N/Abutton.backtoLogin=Back To Login
3853N/Aassertion.consumer-required=Assertion Consumer URL is required.
3853N/Aassertion.consumer-invalid=Assertion Consumer URL is invalid.
3853N/Adomain.is.empty =Domain Name is Empty!
3853N/Aattributemapping.is.empty=Attribute Mapping Table is empty!
3853N/Asp.entity.id.not.specified=Service Provider entity id not specified!
3853N/Aidp.configured=Identity provider is configured.<br />You can modify the provider's profile under the Federation tab.
3853N/Asp.configured=Service provider is configured.<br />You can modify the provider's profile under the Federation tab.
3853N/Ainvalid-extended-data-cot=Unable to get valid set of Circle of Trust because Extended Metadata is invalid.
3853N/Aunable.to.reach.url=Unable to reach, {0}.
3853N/Acannot.locate.idp=Cannot locate Identity Provider, {0}.
3853N/Acannot.locate.idp.loginURL=Cannot locate Login URL for Identity Provider, {0}.
3853N/Acannot.locate.sp=Cannot locate Service Provider, {0}.
3853N/Acannot.locate.sp.loginURL=Cannot locate Login URL for Service Provider, {0}.
3853N/Afederation.connectivity.test=Federation Connectivity Test
3853N/Abutton.cancel=Cancel
3853N/Avalidate.initializing=Please wait while we initialize this test.
3853N/Avalidate.title.setup.failed=Unable to test federation connectivity.
3853N/Avalidate.title.auth.idp=Enter authentication information for Identity Provider, {0}
3853N/Avalidate.help.auth.idp.passed=Authenticated to Identity Provider.
3853N/Avalidate.help.auth.idp.failed=Unable to authenticate to Identity Provider.
3853N/Avalidate.auth.idp.again=Try authenticating again
3853N/Avalidate.title.auth.sp=Enter authentication information for Service Provider. {0}
3853N/Avalidate.help.auth.sp.passed=Authenticated to Service Provider.
3853N/Avalidate.help.auth.sp.failed=Unable to authenticate to Service Provider.
3853N/Avalidate.auth.sp.again=Try authenticating again
3853N/Avalidate.title.account.linking=The system is testing for the ability to link account
3853N/Avalidate.wait.account.linking=Testing for the ability to link account
3853N/Avalidate.help.account.linking.passed=Account is linked
3853N/Avalidate.help.account.linking.failed=Unable to link Account
3853N/Avalidate.title.single.logout=The system is testing for single logout
3853N/Avalidate.wait.single.logout=Testing for single logout
3853N/Avalidate.help.single.logout.passed=Single logout succeeded
3853N/Avalidate.help.single.logout.failed=single logout failed
3853N/Avalidate.title.single.login_hosted=Testing Single Sign On. Enter authentication information for Identity Provider
3853N/Avalidate.title.single.login_remote=Testing Single Sign On. Enter authentication information for Identity Provider
3853N/Avalidate.wait.single.login=Testing for single sign on
3853N/Avalidate.help.single.login.passed=Single sign on is working
3853N/Avalidate.help.single.login.failed=single sign on is not working
3853N/Avalidate.help.single.login.again=Try login again
3853N/Avalidate.title.account.termination=Testing for account termination
3853N/Avalidate.help.account.termination.passed=Account termination is working
3853N/Avalidate.help.account.termination.failed=Account termination is not working
3853N/Avalidate.wait.account.termination=Testing for account termination
3853N/Avalidate.report.title=Connectivity Test Results
3853N/Avalidate.report.task.label.idp=Identity Provider
3853N/Avalidate.report.task.label.sp=Service Provider
3853N/Avalidate.report.task.auth.idp=Identity Provider Authentication
3853N/Avalidate.report.task.auth.sp=Service Provider Authentication
3853N/Avalidate.report.task.account.linking=Account Linking
3853N/Avalidate.report.task.single.logout=Single Log Out
3853N/Avalidate.report.task.single.login=Single Sign On
3853N/Avalidate.report.task.account.termination=Account Unlinking
3853N/Avalidator.report.auth.idp.not.tested=Not Tested
3853N/Avalidator.report.auth.idp.passed=Able to authenticated to IDP.
3853N/Avalidator.report.auth.idp.failed=Unable to authenticated to identity provider. The most common reasons for this failure are:<ol><li>You may have entered an invalid user name or password. If the default setting has not been changed, then you should be able to use "demo" as the user name and "changeit" as the password.</li><li>There may be a configuration error. If you are the Admin, you can check the "amAuth" debug file and "amAuthentication.error" log file for more details.</li></ol>
3853N/Avalidator.report.auth.sp.not.tested=Not Tested
3853N/Avalidator.report.auth.sp.passed=Able to authenticated to SP
3853N/Avalidator.report.auth.sp.failed=Unable to authenticated to service provider. The most common reasons for this failure are:<ol><li>You may have entered an invalid user name or password. If the default setting has not been changed, then you should be able to use "demo" as the user name and "changeit" as the password.</li><li>There may be a configuration error. If you are the Admin, you can check the "amAuth" debug file and "amAuthentication.error" log file for more details.</li></ol>
3853N/Avalidator.report.account.linking.passed=Account Linking successful.
3853N/Avalidator.report.account.linking.failed=Unable to link the accounts. The most common reasons for this error are:<ol><li>The SAMLv2 attribute schema may not be loaded. To correct this error you will need to load SAMLv2 attribute schema file and use the ldapmodify command to load the file which is located inside openam.war as "WEB-INF/template/openfm/fam_sds_schema.ldif"</li><li>You may not have permission to perform this task. You need to contact the administrator to change your permission level.</li><li>The User datastore may not have been configured correctly. To correct this error, go to console, Access Control -> Realms -> Data Stores to make sure the data store is configured correctly. For additional details about data store configuration please reference the administration guide.</li><li>If you are the Admin, you can check the "libSAML2" debug file and "SAML2.error" log file for more details.</li></ol>
3853N/Avalidator.report.single.logout.passed=Single Log Out successful
3853N/Avalidator.report.single.logout.failed=Single Log Out Failed.<ol><li>The session has timed out at the other end you should access the remote endpoint to check if there is valid session.</li><li>There is a connectivity problem. Verify that the endpoint (the URL to access the request) is up and running. The single logout URL is specfied in the metadata.</li></ol><span style="background-color:#333333">If you are the Admin, you can check the "libSAML2" debug file and "SAML2.error" log file for more details</span>
3853N/Avalidator.report.single.login.passed=Single Sign On successful
3853N/Avalidator.report.single.login.failed=Single Sign On Failed. The most common reasons for this failure are:<ol><li>No signing key is configured on identity provider side. You need to re-configure identity provider metadata to have the signing key. NOTE: This only applies if this is POST profile, if this is not a POST profile then this is not the reason for the error.</li><li>The service provider is unable to connect to identity provider using SOAP channel if this is an Artifact profile, you will need to make sure the service provider host is able to connect to identity provider host, this is a typical case in load balancer setup where there are multiple service providers configured behind one load balancer.</li></ol><span style="background-color:#333333">If you are the Admin, you can check the "libSAML2" debug file and "SAML2.error" log file for more details</span>
3853N/Avalidator.report.account.termination.passed=Account Unlinking successful
3853N/Avalidator.report.account.termination.failed=Account Unlinking Failed. The most common reasons for this failure are:<ol><li>There is a connectivity problem. Verify that the endpoint (the URL to access the request) is active; and the single logout URL is specfied in the metadata.</li><li>The user account is not linked on the remote provider, check the account linking on the remote provider. Access your datastore, to check if the both sun-fm-saml2-nameid-infokey and sun-fm-saml2-nameid-info attributes are presented in their entries.</li></ol><span style="background-color:#333333">If you are the Admin, you can check the "libSAML2" debug file and "SAML2.error" log file for more details</span>
3853N/Avalidate.footer.auth.idp=Hint: user name can be demo and password is changeit. Unless default configuration is altered after the product is configured.
3853N/Avalidate.footer.auth.sp=Hint: user name can be demo and password is changeit. Unless default configuration is altered after the product is configured.
3853N/Avalidate.footer.account.linking=Please wait attempting to link user accounts.
3853N/Avalidate.footer.single.logout=Please wait attempting to perform single logout
3853N/Avalidate.footer.single.login=Please login in 30 seconds. Hint: user name can be demo and password is changeit. Unless default configuration is altered after the product is configured.
3853N/Avalidate.footer.account.termination=Please wait attempting to unlink user accounts.
3853N/Avalidator.title.auth.failed=Authentication failed.
3853N/Avalidator.message.auth.failed=The most common reasons for this error are:<ol><li>You may have entered an invalid user name or password. If the default setting has not been changed, then you should be able to use "demo" as the user name and "changeit" as the password.</li><li>There may be a configuration error. If you are the Admin, you can check the "amAuth" debug file and "amAuthentication.error" log file for more details.</li></ol>
3853N/Avalidator.link.auth.failed=Back to Authentication
3853N/AFedlet.created=Your file has been saved to your openam folder: {0}.<p>You can send this file to the Service Provider (or use it locally for demo purposes). The .zip file will enable the SP to become federated as quickly as they can deploy the Fedlet into their application.</p>
3853N/Adirectory.already.exist=Directory {0} already existed.
3853N/Asocial.authn.configured={0} Social Authentication successfully configured.<br/><br/>Created {1} (module)<br/>Created {2} (chain)<br/>Updated {3} (service)
3853N/Amissing-access-token-profile-service-parameter=Missing access token profile service parameter name
3853N/Aauth-module-exists=Cannot create authentication module "{0}" as a module with this name already exists.
3853N/Aauth-chain-exists=Cannot create authentication chain "{0}" as a chain with this name already exists.
3853N/Aoauth2.provider.configured=Successfully configured OAuth2 for realm {0}.<br/>{1}
3853N/Aoauth2.provider.policy.created=A policy was created on the root realm for the authorization end point. The policy name is: {0}
3853N/Aoauth2.provider.policy.exists=A policy for the authorization end point already exists in the root realm with name: {0}
3853N/Aoauth2.provider.policy.failed=An error occurred while trying to create a policy for the authorization end point.
3853N/Aoauth2.provider.resourceType.error=Resource type called URL could not be found for {0} application. Policy was not created.
3853N/Aoauth2.provider.create.error=An error occurred while trying to create the OAuth2 Provider.