Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Scout/JAXWS-RT/Webservice Provider authentication"
< Scout
(New page: {{ScoutPage|cat=JAXWS-RT}} Authentication of webservice requests is not done by Serlvet filters, but webservice handlers instead. Scout provides the following authentication mechanism: * ...) |
|||
| Line 7: | Line 7: | ||
This list is not complete, meaning that you can implement your own authentication mechanism. | This list is not complete, meaning that you can implement your own authentication mechanism. | ||
| − | An authentication handler knows how to extract credentials from within a request. In turn, it passes the requests's credentials to a configured credential validation strategy {{ScoutLink|JAXWS-RT|ICredentialValidationStrategy}} to be validated. This enables you to arbitrary combine an authentication mechanism with | + | An authentication handler knows how to extract credentials from within a request. In turn, it passes the requests's credentials to a configured credential validation strategy ({{ScoutLink|JAXWS-RT|ICredentialValidationStrategy}}) to be validated. This enables you to arbitrary combine an authentication mechanism with a credential validation strategy such as LDAP, database or config.ini. |
Revision as of 18:29, 10 November 2011
The Scout documentation has been moved to https://eclipsescout.github.io/. Authentication of webservice requests is not done by Serlvet filters, but webservice handlers instead. Scout provides the following authentication mechanism:
- The Scout documentation has been moved to https://eclipsescout.github.io/.
- The Scout documentation has been moved to https://eclipsescout.github.io/.
This list is not complete, meaning that you can implement your own authentication mechanism.
An authentication handler knows how to extract credentials from within a request. In turn, it passes the requests's credentials to a configured credential validation strategy (The Scout documentation has been moved to https://eclipsescout.github.io/.) to be validated. This enables you to arbitrary combine an authentication mechanism with a credential validation strategy such as LDAP, database or config.ini.