Click HERE to see how Saviynt Intelligence is transforming the industry. |
06/03/2024 05:54 AM
We have requirement to integrate SAP Concur for operations account creation, update, disable and enable operations.
As per the documentation the account creation operation does not supported, even it is confirmed in the forum post.
Could you please let us know the Saviynt option/Solution to create SAP Concur Account.
https://docs.saviyntcloud.com/bundle/SAPConcur-v24x/page/Content/Supported-Features-v2022x.htm
https://forums.saviynt.com/t5/identity-governance/createaccount-json-sap-concur/m-p/93382#M60822
Thanks
06/03/2024 11:38 AM
You can use external Jar
06/17/2024 05:51 AM
The create for SAP will work thru the Saviynt. I also worked on SAP concur integration and was able to get the createAccount working.
If you are able to get the account created thru postman then you should be able to create it through Saviynt.
06/17/2024 06:41 AM
Can you share working json
06/17/2024 07:00 AM - edited 06/17/2024 07:04 AM
{
"accountIdPath": "call1.message.id",
"call": [
{
"name": "call1",
"connection": "acctAuth",
"url": "https://xyz/Users",
"httpMethod": "POST",
"httpParams": "{\"schemas\":[\"urn:ietf:params:scim:schemas:core:2.0:User\"],\"emails\":[{ \"value\":\${user.email}\",\"type\": \"work\"}],\"active\":true,\"userName\":\"${user.email}\",\"name\":{\"formatted\":\"abc\",\"familyName\":\"abc\",\"givenName\":\"abc\"},\"urn:ietf:params:scim:schemas:extension:spend:2.0:User\":{\"ledgerCode\":\"abc\",\"country\":\"US\",\"locale\":\"en_US\",\"reimbursementCurrency\":\"USD\",\"customData\": [ {\"id\":\"custom21\",\"value\":\"US\"}, {\"id\":\"orgUnit1\",\"value\":\"xyz\"},{\"id\":\"custom20\",\"value\":\"xyz\"},{\"id\":\"orgUnit4\",\"value\":\"xyz\"},{\"id\":\"orgUnit2\",\"value\":\"xyz\"},{\"id\":\"custom1\",\"value\":\"apitest@xyz.com\"}]},\"urn:ietf:params:scim:schemas:extension:enterprise:2.0:User\":{\"employeeNumber\":\"${user.email}\", \"companyId\":\"xyz\"},\"urn:ietf:params:scim:schemas:extension:spend:2.0:Role\":{\"roles\":[{\"roleName\": \"role1\"},{\"roleName\": \"role2\"},{\"roleName\": \"role3\"},{\"roleName\": \"role4\"}]}}",
"httpHeaders": {
"Authorization": "${access_token}",
"Accept": "application/json"
},
"httpContentType": "application/json",
"successResponses": {
"statusCode": [
200
]
},
"unsuccessResponses": {
"statusCode": [
400,
401,
404,
500,
501,
502,
503,
504
]
}
}
]
}
07/09/2024 11:40 PM
Hi @ghrk @Rajatlm10 @rushikeshvartak ,
This seems to be a simple straight forward JSON to create users in SAP concur via Saviynt. Do you have any idea why this is not documented in the supported features list in the documentation?
Hi @Darshanjain , can you please share your inputs here.
Thanks
07/09/2024 11:42 PM
Provide feedback on documentation
08/01/2024 11:28 AM
We are also looking for concur integration, just wanted to confirm if create account and adding access (roles/entitlements) supported or not. Were you able to implement these use cases successfully. We are on version 24.5. Thank You!
08/01/2024 10:26 PM
Hi @rajsannidhi ,
The create account part is supported on Concur API v4.
The Saviynt documentation Supported Software Versions (saviyntcloud.com) has mentioned the usage of Concur API v3 and hence it says that create account is not supported.
But since we are using a plain ootb REST connector in Saviynt for Concur, we can achieve create account by using v4 APIs of concur; I believe that's what @Rajatlm10 has used.
I am not sure if adding access (roles/entitlements) is supported or not, but if APIs are available, it should work.
08/13/2024 01:11 PM
Can we directly integrate with concur PROD instance, does concur allow us to test API calls directly in PROD?
Is it mandatory for setting 3rd party app integration with a sandbox environment first, test API calls and then promote the app to PROD.
08/13/2024 01:14 PM
This is ideal practice you should first validate all application with sandbox then move to PROD. to avoid large user impact
08/13/2024 01:18 PM
I agree with you, just checking because our customer doesn't have concur test instance, so wanted to know if concur allows to do it or not, based on what I found I think they would want us to test with sandbox first. Just looking for confirmation.
08/02/2024 07:07 AM
@haardik_verma Thank you for providing the details.
@rushikeshvartak Provided Feedback on the documentation.
09/20/2024 09:49 AM - last edited on 09/20/2024 10:29 AM by Dave
Hi @haardik_verma @rushikeshvartak
Our customer has created a sandbox environment, I tried using Application Integration, what is the x-consumer key, is it client secret?
can you please confirm which authentication should we use, is it Authorization grant or Password Grant. Can you please share a sample connection JSON if we can use Authorization Grant. Thank you for help and support.
[This post has been edited by a Moderator to remove sensitive information.]
09/20/2024 09:53 AM
x-consumer key: This is typically the API key or client ID provided when you register your application. It is not the same as the client secret.
Authentication Method: The choice between Authorization Grant and Password Grant depends on your application's requirements.
09/20/2024 10:28 AM - last edited on 09/20/2024 11:07 AM by Dave
@rushikeshvartak Thank for quick response. So, we can update the connection JSON after the connection is created accordingly with the grant type we are using.
Because the application onboarding only has username and password options but with authorization grant, we need to provide access and refresh tokens. Can you please review below connection JSON for authorization grant, based on SAP Concur Developer Center | Authentication I think we don't need Authorization in "httpHeaders":
{
"authentications": {
"acctAuth": {
"authType": "oauth2",
"url": "https://*****.api.concursolutions.com",
"httpMethod": "POST",
"httpParams": {
"grant_type": "refresh_token",
"refresh_token": "${refresh_token}"
},
"httpHeaders": {
"Content-Type": "application/x-www-form-urlencoded",
"Authorization": "Basic xxxxxxyyyyyyyyzzzzzz"
},
"httpContentType": "application/x-www-form-urlencoded",
"expiryError": "ExpiredAuthenticationToken",
"authError": [
"USER_AUTHENTICATION_FAILED",
"PARTNER_AUTHENTICATION_FAILED",
"AuthenticationFailed"
],
"refreshType": "RefreshToken",
"refreshTokenResponsePath":"refresh_token",
"refreshToken":"xxxxxxyyyyyyyyzzzzzz",
"timeOutError": "Read timed out",
"errorPath": "errorCode",
"maxRefreshTryCount": 5,
"tokenResponsePath": "access_token",
"tokenType": "Bearer",
"retryFailureStatusCode": [
401
],
"accessToken":"Bearer xxxxxxyyyyyyyyzzzzzz"
}
}
}
[This post has been edited by a Moderator to remove sensitive information.]
09/20/2024 10:41 AM
09/23/2024 11:49 AM
@rushikeshvartak In the documentation, connection JSON only has username and password options but no JSON for authorization grant. Also, create account JSON is not available. Can this be added to the documentation. Thank You!
09/23/2024 12:13 PM
Please add feedback on documentation page https://docs.saviyntcloud.com/bundle/Doc-Site-Help/page/Content/Sharing-your-feedback.htm
09/23/2024 12:24 PM
@rushikeshvartak Provided feedback. Thank you!