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

ASF GitHub Bot updated AMBARI-23440:
------------------------------------
    Labels: SSO pull-request-available security  (was: SSO security)

> 404 error while setting up SSO on a new cluster 
> ------------------------------------------------
>
>                 Key: AMBARI-23440
>                 URL: https://issues.apache.org/jira/browse/AMBARI-23440
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.7.0
>            Reporter: Sandor Molnar
>            Assignee: Sandor Molnar
>            Priority: Critical
>              Labels: SSO, pull-request-available, security
>             Fix For: 2.7.0
>
>
> When setting up SSO via the Ambari server CLI using a new Ambari server 
> instance, the following error is encountered:
> {noformat}
> [root@c7401 ~]# ambari-server setup-sso
> Using python  /usr/bin/python
> Setting up SSO authentication properties...
> Enter Ambari Admin login: admin
> Enter Ambari Admin password:
> Fetching SSO configuration from DB.ERROR: Exiting with exit code 1.
> REASON: Error while fetching SSO configuration. Error details: HTTP Error 
> 404: Not Found
> {noformat}
> This is caused by the lack of the {{sso-configuration}} category in the 
> Ambari configuration set - which will be a common scenario for new Ambari 
> clusters.
> {noformat}
> GET 
> /api/v1/services/AMBARI/components/AMBARI_SERVER/configurations/sso-configuration
> {noformat}
> {noformat}
> {
>   "status" : 404,
>   "message" : "The requested resource doesn't exist: 
> RootServiceComponentConfiguration not found where 
> Configuration/service_name=AMBARI AND 
> Configuration/component_name=AMBARI_SERVER AND 
> Configuration/category=sso-configuration."
> }
> {noformat}
> The CLI handle this response and assume the following default values:
> {noformat}
> ambari.sso.manage_services = false
> ambari.sso.enabled_services = 
> {noformat}
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to