Security Check

The security check call is equivalent to a login call. You send the user credentials and you can tell from the response whether they are valid or not on the server. If they are valid, the server creates a user session or if the user has already performed an operation with valid credentials, it accesses the existing user session.

In either case, the successful response contains the JSESSIONID cookie of the user session. As with the login service, once you receive the session cookie, you should return it with future requests and use it to close the session as described in Logout.

If you specify accept: application/json in your request, the location of the redirect in case of success is always the file /scripts/bower_components/js-sdk/src/common/auth/loginSuccess.json. The content of this file is:

{
"success":true
}

You can configure the location of this file. Edit the configuration file applicationContext-security-web.xml and change the constructor value of the following bean:

<bean id="authSuccessJsonRedirectUrl" class="java.lang.String">
 
  <constructor-arg type="java.lang.String"
    value="/scripts/bower_components/js-sdk/src/common/auth/loginSuccess.json"/>
 
</bean>

Using an SSO Token

If you are using Single Sign-On for authentication, you can use the security check to submit the ticket.

For example, if you have configured the server to use CAS as your SSO provider, you can authenticate and receive the session ID with the following request:

The response has the same behavior as the password-based security check, including the use of a JSON file if requested.

Using a Pre-Authentication Token

When using a pre-authentication mechanism, the verification of the credentials is performed at the base URL of the server.

For example, if you have configured the server to use pre-authentication, you can authenticate and receive the session ID with the following request: