SAP Knowledge Base Article - Preview

2461997 - Adding Neo subaccount to SAP Cloud Connector fails due to authorization error


When adding an SAP Cloud Platform Neo subaccount to SAP Cloud Connector, the following error is displayed on the screen:

417 An authorization problem occurred when downloading the configuration. Check the spelling of the subaccount name, user, and password — see ''Logs'' for details


When checking the Logs for details, an error similar to the following one is recorded: #Creating an sslContextProvider for account <subaccount>@<region> without SSLContext. Keystore did not contain a certificate.| #New RSA keypair was generated. Key size used: 4096| #Will retrieve Connectivity CA certificate from SAP HANA Cloud| #Executing Http Get request to https://connectivitycertsigning.<region>:443/certificate/management/v1/trusted/ca/account/<subaccount>|
#WARN#org.apache.http.impl.client.DefaultHttpClient#http-bio-8443-exec-7# #Authentication error: basic authorization challenge expected, but not found| #Returned Http Response with code 401| #sccEndpoint ok, and context == null| #SCC handshake failed: 401 - Unauthorized SCC handshake failed: 401 - Unauthorized

Note: In case of a Cloud Foundry subaccount, refer to KBA 2571763 instead.



  • SAP Cloud Connector
  • SAP Cloud Platform, Neo environment
  • Identity Authentication


SAP Connectivity service all versions


scc s-user, Invalid status of handshake response: 401 Unauthorized , KBA , unable to add a cloud foundry , subaccount(sac) in sap cloud connector , sac , cc , BC-MID-SCC , SAP Cloud Connector On-Demand/On-Premise Connectivity , BC-NEO-SEC-IAM , Authentication, Authorization(Cloud Platform Neo) , BC-NEO-CON , Neo to On-premise Connectivity service , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.