You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "Sandor Molnar (Jira)" <ji...@apache.org> on 2025/09/09 12:00: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 ]
Sandor Molnar updated KNOX-1741:
--------------------------------
Fix Version/s: 3.0.0
(was: 2.1.0)
Due to the pending 2.1.0 release this JIRA has been pushed out to 3.0.0 as part of a bulk update. If there is a specific reason to pull this back into the 2.1.0 release and you intend to provide a PR in the next few days please provide justification and reset the Fix Version to 2.1.0.
> 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: 3.0.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:
> # 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. This will be similar to the Okta portal page with tiles for UIs and Services.
> # KnoxSSO protection of the landing page to insure that the user is logged in
> # 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.
> # 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 or meaningful rendering of JSON in a tree or table.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)