[
https://issues.apache.org/jira/browse/AMBARI-23262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-23262:
----------------------------------
Description:
Create \{{sso-configuration}} category in Ambari Configurations data and allow
for the {{ambari.sso.enabled_services}} property to be added to it. This
property is used to declare what services are expected to be configured for SSO
and is expected to be a comma-delimited list of services or "{{*}}" to indicate
all services.
Examples:
{code:title=All services}
"ambari.sso.enabled_services":"*"
{code}
{code:title=Only Ambari}
"ambari.sso.enabled_services":"Ambari"
{code}
{code:title=Ambari, Ranger, and Atlas}
"ambari.sso.enabled_services":"Ambari, Ranger, Atlas"
{code}
Each service in the set of services should have indicated it supports SSO (see
AMBARI-23252) else it will silently be ignored.
This value should be set via Ambari's REST API or a Blueprint.
Upon setting this value via the Ambari REST API, it is expected that internal
logic will be triggered to ensure the relevant services in the list are
configured for SSO or not configured for SSO as the case may be.
was:
Create \{{sso-configuration}} category in Ambari Configurations data and allow
for the \{{sso_enabled_services}} property to be added to it. This property is
used to declare what services are expected to be configured for SSO and is
expected to be a comma-delimited list of services or "\{{*}}" to indicate all
services.
Examples:
{code:title=All services}
"sso_enabled_services":"*"
{code}
{code:title=Only Ambari}
"sso_enabled_services":"Ambari"
{code}
{code:title=Ambari, Ranger, and Atlas}
"sso_enabled_services":"Ambari, Ranger, Atlas"
{code}
Each service in the set of services should have indicated it supports SSO (see
BUG-98626) else it will silently be ignored.
This value should be set via Ambari's REST API or a Blueprint.
Upon setting this value via the Ambari REST API, it is expected that internal
logic will be triggered to ensure the relevant services in the list are
configured for SSO or not configured for SSO as the case may be.
> Create sso-configuration category in Ambari Configurations data
> ---------------------------------------------------------------
>
> Key: AMBARI-23262
> URL: https://issues.apache.org/jira/browse/AMBARI-23262
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
> Affects Versions: 2.7.0
> Reporter: Robert Levas
> Assignee: Robert Levas
> Priority: Major
> Fix For: 2.7.0
>
>
> Create \{{sso-configuration}} category in Ambari Configurations data and
> allow for the {{ambari.sso.enabled_services}} property to be added to it.
> This property is used to declare what services are expected to be configured
> for SSO and is expected to be a comma-delimited list of services or "{{*}}"
> to indicate all services.
> Examples:
> {code:title=All services}
> "ambari.sso.enabled_services":"*"
> {code}
> {code:title=Only Ambari}
> "ambari.sso.enabled_services":"Ambari"
> {code}
> {code:title=Ambari, Ranger, and Atlas}
> "ambari.sso.enabled_services":"Ambari, Ranger, Atlas"
> {code}
> Each service in the set of services should have indicated it supports SSO
> (see AMBARI-23252) else it will silently be ignored.
> This value should be set via Ambari's REST API or a Blueprint.
> Upon setting this value via the Ambari REST API, it is expected that internal
> logic will be triggered to ensure the relevant services in the list are
> configured for SSO or not configured for SSO as the case may be.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
