[ 
https://issues.apache.org/jira/browse/FEDIZ-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Wulff updated FEDIZ-52:
------------------------------

    Description: 
The authentication type can be configured in the Fediz plugin statically or a 
callback handler can be implemented and configured.

This is a default implementation of a callback handler to pass the wauth 
parameter in the SignIn request to the IDP in the initial request to the 
application:
https://localhost:8443/fedizhelloworld/secure/fedservlet?wauth=xyz

See here for a list of standard authentication types:
http://docs.oasis-open.org/wsfed/federation/v1.2/os/ws-federation-1.2-spec-os.html#_Toc223174997


  was:Fediz plugin supports out-of-the-box the whr parameter in the initial 
request to the RP. This allows the browser to tell the home realm discovery 
service who the requestor IDP is.

     Issue Type: Improvement  (was: Bug)
        Summary: Support wauth parameter in initial request to RP  (was: 
Support whr parameter in initial request to RP)
    
> Support wauth parameter in initial request to RP
> ------------------------------------------------
>
>                 Key: FEDIZ-52
>                 URL: https://issues.apache.org/jira/browse/FEDIZ-52
>             Project: CXF-Fediz
>          Issue Type: Improvement
>          Components: Plugin
>    Affects Versions: 1.1.0
>            Reporter: Oliver Wulff
>
> The authentication type can be configured in the Fediz plugin statically or a 
> callback handler can be implemented and configured.
> This is a default implementation of a callback handler to pass the wauth 
> parameter in the SignIn request to the IDP in the initial request to the 
> application:
> https://localhost:8443/fedizhelloworld/secure/fedservlet?wauth=xyz
> See here for a list of standard authentication types:
> http://docs.oasis-open.org/wsfed/federation/v1.2/os/ws-federation-1.2-spec-os.html#_Toc223174997

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to