CELUM Token Verifier

For the most up-to-date documentation, please visit docs.brix.ch

One of the TokenVerifiers we provide out-of-the-box is one that lets you authenticate agains CELUM. Additionally, you can also decide which Anura endpoint a user should use based on group assignments in CELUM. Note however that the endpoint still uses its configured user - in other words this does not enable you to do user-level permissions or statistics.

Installation

Grab the anura-login-token-{version}.jar and put it in {home}/appserver/lib. You may now use anuraLoginTokenVerifier in anura.1.tokenVerifier and this snippet in your front-end.

Properties

anuraLoginToken.endPointToUserGroupMap

type: Map{String, List{Long}}, required: no, default: null

This allows you to map endpoints to user groups. In other words you can dynamically decide which Anura endpoint an authenticating user should be using for this session. Specify the endpoints with the most rights first because if a user is in several groups, he will get the first end point that was found.

Example: foo:1,2,3;bar:4,5,6;baz:7,8,9 assigns the endpoint foo to users that are in groups 1, 2 or 3, etc.

anuraLoginToken.expiresAfterNoAccessForMinutes

type: int, required: no, default: 30

Number of minutes with no access until the token expires.

anuraLoginToken.forceExpirationMinutesAfterCreation

type: int, required: no, default: 300

Number of minutes after creation whereafter a token is forced to expire, regardless of access.

anuraLoginToken.validChars

type: String, required: no, default: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789_-

Characters used for the token generation, they have to be valid in an URL without encoding

anuraLoginToken.tokenLength

type: int, required: no, default: 32

The length (number of characters) of the token that will be generated

Release Notes

1.0.0

Released: 14.01.2019

Initial release