<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D54z00008zmI7VCAUOkta Classic EngineIntegrationsAnswered2024-04-17T10:44:44.000Z2023-03-31T02:00:39.000Z2023-04-03T04:29:49.000Z

gojrb (gojrb) asked a question.

Okta SCIM Enable API Integration with SCIM Connector for Delinea's Secret Server Cloud

Hello,

I am trying to add SCIM 2.0 Test App (Header Auth) For delinea secret server.

I have SCIM Connector for Secret Server hosted on one of the EC2 instance in AWS.

When I am trying to enable API integration, I am receiving errors where as when I am trying the same Base URL and Token from Postman with marking that token as Bearer token, it works. Need Okta's help in understanding what is wrong with the my configuration

When I add "Bearer " or "Bearer=" infront of the token, I get following error.

  • Error authenticating: Unauthorized
  • Error authenticating: Internal Server Error.Please Contact your Administrator.. Errors reported by remote server:

 

But these do work from Postman and I am able to see the response.

 


  • User16594883467582706479 (Customer Support Online Experience)

    Hi, @gojrb (gojrb)​ 

     

    Thank you for posting on our Community page!

     

    Whatever value is put into the Authorization field is what Okta will send in the Authorization header when making calls to your SCIM server.

     

    For example, if in Postman you set the Authorization header to "Bearer token1234" then thats the exact same value you should provide Okta for the Authorization field.

     

    Thank you for reaching out to our Community and have a great day!

     

    _____________________________________________________________________________

    Community members help others by clicking Like or Select as Best on responses. Try it today.

    _____________________________________________________________________________

    Expand Post
    Selected as Best
  • User16594883467582706479 (Customer Support Online Experience)

    Hi, @gojrb (gojrb)​ 

     

    Thank you for posting on our Community page!

     

    Whatever value is put into the Authorization field is what Okta will send in the Authorization header when making calls to your SCIM server.

     

    For example, if in Postman you set the Authorization header to "Bearer token1234" then thats the exact same value you should provide Okta for the Authorization field.

     

    Thank you for reaching out to our Community and have a great day!

     

    _____________________________________________________________________________

    Community members help others by clicking Like or Select as Best on responses. Try it today.

    _____________________________________________________________________________

    Expand Post
    Selected as Best
  • gojrb (gojrb)

    Hello @User16594883467582706479 (Customer Support Online Experience)​ ,

     

    I have tried this and I still get error -

    • Error authenticating: Internal Server Error.Please Contact your Administrator.. Errors reported by remote server:

     

    As I mentioned earlier, I dont get this kind of error in Postman

    I have already tried all of below

    • bearer token122332
    • Bearer token122332
    • Bearer=token122332
    • bearer=token122332
    • Bearer Token token122332

     

    None of these seem to work.

    Expand Post
  • gojrb (gojrb)

    I get below error from application log -

     

     {

      "RequestURI": "https://custom-url/SCIMConnector/SSEndpoint/Users?startIndex=1&count=2",

      "Action": "GET",

      "User": null,

      "DateTime": "2023-04-02T02:53:28.683062+11:00",

      "ResponseStatus": 500,

      "Message": "Message: Operator '==' cannot be applied to operands of type 'string' and 'int', StackTrace:  at CallSite.Target(Closure, CallSite, Object, Int32)\r\n at SCIM.Controllers.SSEndpointController.<>c__DisplayClass3_0.<Get>b__0(SSEndpoint u) in D:\\a\\1\\s\\SCIM\\SCIM\\Controllers\\SSEndPointController.cs:line 49\r\n at System.Linq.Enumerable.TryGetFirst[TSource](IEnumerable`1 source, Func`2 predicate, Boolean& found)\r\n at System.Linq.Enumerable.FirstOrDefault[TSource](IEnumerable`1 source, Func`2 predicate)\r\n at SCIM.Controllers.SSEndpointController.Get(Int32 id) in D:\\a\\1\\s\\SCIM\\SCIM\\Controllers\\SSEndPointController.cs:line 49\r\n at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.TaskOfIActionResultExecutor.Execute(ActionContext actionContext, IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Object[] arguments)\r\n at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.<InvokeActionMethodAsync>g__Awaited|12_0(ControllerActionInvoker invoker, ValueTask`1 actionResultValueTask)\r\n at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.<InvokeNextActionFilterAsync>g__Awaited|10_0(ControllerActionInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)\r\n at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Rethrow(ActionExecutedContextSealed context)\r\n at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)\r\n at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.<InvokeInnerFilterAsync>g__Awaited|13_0(ControllerActionInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)\r\n at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeNextExceptionFilterAsync>g__Awaited|26_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)",

      "Origin": “custom-url”

     }

    Expand Post
This question is closed.
Loading
Okta SCIM Enable API Integration with SCIM Connector for Delinea's Secret Server Cloud