AnsweredAssumed Answered

Option to pass the OAuth token along with the SCIM  connector or collector

Question asked by Shanti Deepak on Sep 4, 2019

Hi,

 

I am trying to integrate facebook's workplace with the IGL. The current scenario is the workplace supports SCIM based provisioning. I am also able to provision (Create a User using the Postman  with SCIM based api) 

 

The base URL for the Account Management API(SCIM): https://www.facebook.com/scim/v1/users
The base URL for the Account Management API(GRAPH): https://www.graph.facebook.com/company/Accounts

https://www.facebook.com/scim/v1/users

 

This works fine with the Postman using the access_token mechanism along with the API request.

 

However, In the IGL's SCIM based connector and collector, we need to pass Admin Username and Password we tried with the same but getting the error:

 

2019-09-04 16:09:54.845 [INFO] com.aveksa.AFX.server.runtime.esb.scim.service.HttpBasicAuthenticationScheme:193 - Authentication Scheme is http basic and authoraization header is Basic c2hhbnRpLmRlZXBha0B0YXRhYWR2YW5jZWRzeXN0ZW1zLmNvbTpTYW5kQDEyMw==
2019-09-04 16:09:57.026 [WARN] org.apache.commons.httpclient.HttpMethodBase:265 - Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended.
2019-09-04 16:09:57.027 [ERROR] com.aveksa.AFX.transport.scim.SCIMSettingsTest:50 - Error occured due to : com.scim.exception.SCIMException: Server responded with error code 401 and response : {
"Errors": [
{
"description": "Unauthorized Access: Access to this resource is forbidden.",
"code": 1789001
}
]
}

 

So, what I am looking for here is, if it is possible to use the OAuth (Token) based authentication instead of HttpBasicAuthenticationScheme for the SCIM based connector and collector.

 

I am looking for an option where we can pass the OAuth token along with the SCIM  based API request.

 

Attached snapshots for the reference.

 

Please help.

 

Thanks,

Deepak

Attachments

Outcomes