You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "Larry McCay (JIRA)" <ji...@apache.org> on 2019/01/20 15:16:00 UTC
[jira] [Updated] (KNOX-1741) KnoxSSO to Support IDP Initiated Flow
[ https://issues.apache.org/jira/browse/KNOX-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Larry McCay updated KNOX-1741:
------------------------------
Description:
Currently, KnoxSSO is constrained to an SP Initiated Flow - meaning, the user must attempt to access a participating application before s/he is redirected to an IdP for authentication.
This restriction has been problematic for some deployments that have multiple tenants or realms since the participating application has only a single URL to redirect to when authentication is required.
This JIRA is an umbrella for a few tasks in order to enable the following:
1. A landing page that displays a portal of available Topologies and then services/UIs within each. Need to determine which topologies to inclulde - maybe only those protected by KnoxSSO - which will require some Admin API calls.
2. KnoxSSO protection of the landing page to insure that the user is logged in
3. A login form that includes username, password and realm - or perhaps a top level page that requires realm only. This can become the URL that participating application redirect the user to when a new authentication is required.
4. Clicking into a Service rather than a UI should result in a REST Client Page where the KnoxSSO token will be presented and results returned in a scrollable textarea
was:
Currently, KnoxSSO is constrained to an SP Initiated Flow - meaning, the user must attempt to access a participating application before s/he is redirected to an IdP for authentication.
This restriction has been problematic for some deployments that have multiple tenants or realms since the participating application has only a single URL to redirect to when authentication is required.
This JIRA is an umbrella for a few tasks in order to enable the following:
1. A landing page that displays a portal of available Topologies and then services/UIs within each. Need to determine which topologies to inclulde - maybe only those protected by KnoxSSO - which will require some Admin API calls.
2. KnoxSSO protection of the landing page to insure that the user is logged in
3. A login form that includes username, password and realm - or perhaps a top level page that requires realm only. This can become the URL that participating application redirect the user to when a new authentication is required.
> KnoxSSO to Support IDP Initiated Flow
> -------------------------------------
>
> Key: KNOX-1741
> URL: https://issues.apache.org/jira/browse/KNOX-1741
> Project: Apache Knox
> Issue Type: Improvement
> Components: KnoxSSO
> Reporter: Larry McCay
> Priority: Major
> Fix For: 1.3.0
>
>
> Currently, KnoxSSO is constrained to an SP Initiated Flow - meaning, the user must attempt to access a participating application before s/he is redirected to an IdP for authentication.
> This restriction has been problematic for some deployments that have multiple tenants or realms since the participating application has only a single URL to redirect to when authentication is required.
> This JIRA is an umbrella for a few tasks in order to enable the following:
> 1. A landing page that displays a portal of available Topologies and then services/UIs within each. Need to determine which topologies to inclulde - maybe only those protected by KnoxSSO - which will require some Admin API calls.
> 2. KnoxSSO protection of the landing page to insure that the user is logged in
> 3. A login form that includes username, password and realm - or perhaps a top level page that requires realm only. This can become the URL that participating application redirect the user to when a new authentication is required.
> 4. Clicking into a Service rather than a UI should result in a REST Client Page where the KnoxSSO token will be presented and results returned in a scrollable textarea
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)