Page History
...
Specific Provider Configurations
WhiteBlackListAttrProvider:
The WhiteBlackListAttrProvider queries a database's table of whitelisted and blacklisted users. Its typical configuration follows.
...
Code Block | ||||
---|---|---|---|---|
| ||||
wb-list: -> { isBlack -> (true/false}, isWhite -> (true/false} } |
EndpointAttrProvider
An EndpointAttrProvider fetches data from a remote URL and extracts attributes from that data by using Regexes. As an example is extracts 2 attributes, person_id and faculty_type:
...
Code Block | ||||
---|---|---|---|---|
| ||||
endpoint_everything -> { everything: [...] } |
RequestHeadersAttrProvider
The RequestHeadersAttrProvider extracts values from HTTP request headers:
...
Code Block | ||||
---|---|---|---|---|
| ||||
headers -> { AJP_userId: [...] AJP_email: [...] AJP_firstName: [...] AJP_lastName: [...] } |
HmsAuthorizer
The authorization provider, for example, HmsAuthorizer, makes use of the attributes generated by the attribute providers.
Code Block | ||||
---|---|---|---|---|
| ||||
authorizer : { name : net.shrine.authz.providerService.authorize.HmsAuthorizer } |
RegexAuthorizer
A more flexible authorization provider could be the RegexAuthorizer. It concatenates all the received attributes and values, and then applies any number of Regexes to it. Authorization is granted if all regexes find a match. A "!" before a Regex means that there should not be a match.
...