| Include Page | ||||
|---|---|---|---|---|
|
| Info |
|---|
For Grouper 2.5 and above see this wiki page |
High level Grouper WS authentication
...
| Code Block |
|---|
# prepend to the userid this value (e.g. if using local entities, might be: etc:servicePrincipals: ) ws.security.prependToUserIdForSubjectLookup = etc:servicePrincipals: |
Hit a link: login as test_local_entity and whatever_pass
...
| Code Block |
|---|
./gsh scriptName.gsh |
...
Default authentication
Out of the box, grouper-ws uses container authentication (non-rampart). The web.xml protects all services and expects the users to be in the role "grouper_user". For tomcat, in the tomcat-users.xml, just have entries like this, and you are all set:
...