UI Authentications

Translate5 default login page

The LoginController provides a page with login and password form, where a user can provide his credentials and is authenticated then.

The usual way to get in translate5.

Single Sign On

See single sign on page, using a centralized login page.

IP based authentication

See IpAuthentication, useful only for TermPortal and InstantTranslation

• Must be enabled by configuration for a range of fixed IP addresses
• Creates an anonymous user per session

API based authentications

Session API endpoint

See Session

• POSTing username and password to the SessionController returns a new session and as an alternative a one time token
• The new session
  • can be used directly by using the returned session ID
  • can be retrieved by using the one time token

Session impersonate endpoint

See Session

• Each user with API role can transform its current session into the session of another existing user.

Single click authentication (job based)

See Single Click Authentication

• Must be enabled by configuration
• either with a dynamic hash
• or with a static hash
• the hash must be retrieved from the Task User Associations API endpoint

API token

See Application Token.

• An API token can be generated per user.
• The token can be used at all places where the password is entered instead of the password to generate a new session
• Or session independent as HTTP Header "Translate5AuthToken"

CLI based authentication

See ./translate5.sh auth:impersonate

• The CLI command auth:impersonate is authentication each user with access to the server as each existing user.
• Under the hood the session based one time token is used