External authentication interface for mobile applications

The standard EAI flow can involve multiple Moved Temporarily (302) operations, which are not mobile application friendly. WebSEAL provides configuration options to help reduce the number of 302 operations.

The following topics illustrate the various scenarios based on the authentication information transport mechanism.

• Authentication through 401 WWW-Authenticate
  Use this scenario as an example where the authentication information is provided as an HTTP header, for example, basic-authentication.
• Authentication through forms
  Use this flow as an example to reduce 302 operations for forms authentication.

Parent topic: External authentication interface