sailpoint SCIM - query all users

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

sailpoint SCIM - query all users

L4 Transporter

When I try to query all users, it fails with the error - {"code":500,"message":"There was an error processing your request. It has been logged (ID af52cf0f244cfbd3)."}

But if I put a filter and query for an individual user, it works fine.

 

In the CAScimServer.log file, I could see the below -

 

EBUG|21/06/28 16:19:08.913|CyberarkBasicAuthenticator|authenticate|23|dw-32 - GET /CyberArk/scim/v2/Users/|Basic Authenticator

DEBUG|21/06/28 16:19:09.002|PACLI|execute|221|dw-32 - GET /CyberArk/scim/v2/Users/|==> Using Cache for USERSLIST USERPATTERN="*" OUTPUT(OEM,ENCLOSE,USERID,NAME,TYPE,LOCATION,TEMPLATE)

DEBUG|21/06/28 16:19:09.029|UserGroupService|list|82|dw-32 - GET /CyberArk/scim/v2/Users/|==> Size of tempRecords 240 batchSize: 240

DEBUG|21/06/28 16:19:09.029|UserGroupService|list|88|dw-32 - GET /CyberArk/scim/v2/Users/|*** Number of Batches: 1

DEBUG|21/06/28 16:19:09.030|PACLI|execute|221|dw-32 - GET /CyberArk/scim/v2/Users/|==> Using Cache for USERDETAILS DESTUSER="Master" OUTPUT(RAW,ENCLOSE,NAME,FIRSTNAME,LASTNAME,MIDDLENAME,PASSAUTH,PKIAUTH,SECUREIDAUTH,NTAUTH,RADIUSAUTH,DISABLED,JOBTITLE,LDAPUSER,HEMAIL,BEMAIL,OEMAIL,HOMESTREET,HOMECITY,HOMESTATE,HOMECOUNTRY,HOMEZIP,WORKSTREET,WORKCITY,WORKSTATE,WORKCOUNTRY,WORKZIP,HOMEPHONE,WORKPHONE,CELLULAR,FAX,PAGER,ORGANIZATION,DEPARTMENT,LOCATION,PROFESSION,HOMEPAGE,USERAUTH,USERTYPEID,FROMHOUR,TOHOUR,EXPIRATIONDATE,LDAPDIRECTORY,LDAPFULLDN,TEMPLATE) 

 

CASCIMServer - Audit log

[06/28/2021 16:19:09] User SailPoint-user Succesfully Authenticated.

[06/28/2021 16:19:09] User SailPoint-user URI: http://xxxx:8080/CyberArk/scim/v2/Users/ Method:GET Query:[null]

 

CASCIMServer-STDOUT log

 

[06/28/2021 16:19:09] Error handling a request: 0c39381b51e3e666

java.lang.NullPointerException: null

at com.cyberark.scimserver.services.UserService.createDetailsResourceFromRecord(UserService.java:176)

at com.cyberark.scimserver.services.UserService.createListResourceFromRecord(UserService.java:118)

at com.cyberark.scimserver.services.UserService.createListResourceFromRecord(UserService.java:41)

at com.cyberark.scimserver.services.UserGroupService.list(UserGroupService.java:131)

at com.cyberark.scimserver.services.UserService.list(UserService.java:359)

at com.cyberark.scimserver.resources.UserListResource.list(UserListResource.java:81)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory$1.invoke(ResourceMethodInvocationHandlerFactory.java:81)

at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:144)

at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:161)

at org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$TypeOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:205)

at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch(AbstractJavaResourceMethodDispatcher.java:99)

at org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:389)

at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:347)

at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:102)

at org.glassfish.jersey.server.ServerRuntime$2.run(ServerRuntime.java:326)

at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271)

at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267)

at org.glassfish.jersey.internal.Errors.process(Errors.java:315)

at org.glassfish.jersey.internal.Errors.process(Errors.java:297)

at org.glassfish.jersey.internal.Errors.process(Errors.java:267)

at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:317)

at org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:305)

at org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:1154)

at org.glassfish.jersey.servlet.WebComponent.serviceImpl(WebComponent.java:473)

at org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:427)

at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:388)

at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:341)

at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:228)

at io.dropwizard.jetty.NonblockingServletHolder.handle(NonblockingServletHolder.java:49)

at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1623)

at io.dropwizard.servlets.ThreadNameFilter.doFilter(ThreadNameFilter.java:35)

at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610)

at io.dropwizard.jersey.filter.AllowedMethodsFilter.handle(AllowedMethodsFilter.java:45)

at io.dropwizard.jersey.filter.AllowedMethodsFilter.doFilter(AllowedMethodsFilter.java:39)

at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610)

at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:540)

at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255)

at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1345)

at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:203)

at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:480)

at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:201)

at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1247)

at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:144)

at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)

at com.codahale.metrics.jetty9.InstrumentedHandler.handle(InstrumentedHandler.java:239)

at io.dropwizard.jetty.RoutingHandler.handle(RoutingHandler.java:52)

at org.eclipse.jetty.server.handler.gzip.GzipHandler.handle(GzipHandler.java:753)

at io.dropwizard.jetty.BiDiGzipHandler.handle(BiDiGzipHandler.java:67)

at org.eclipse.jetty.server.handler.RequestLogHandler.handle(RequestLogHandler.java:56)

at org.eclipse.jetty.server.handler.StatisticsHandler.handle(StatisticsHandler.java:174)

at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)

at org.eclipse.jetty.server.Server.handle(Server.java:505)

at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:370)

at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:267)

at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:305)

at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103)

at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:117)

at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:333)

at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:310)

at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:168)

at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.produce(EatWhatYouKill.java:132)

at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:698)

at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:804)

at java.lang.Thread.run(Unknown Source)

 

 

As per the CAScimServer.log file, not sure whether it is trying to get the user details for master. But I have already added this user to ignore users list in GlobalConfig.yml file.

 

Could someone advise on this.

 

7 REPLIES 7

L4 Transporter

Run PACLI manually to fetch MASTER user details with the SailPoint account & and see if you something weird. Probably something in the output that SCIM server isn't able to handle

L4 Transporter

@Pranav Chugh​  I tried to run the query against master account and it failed with the error "{"schemas":["urn:ietf:params:scim:api:messages:2.0:Error"],"status":500,"detail":"ERROR -> ITATS007E You are not authorized to get details of User Master."}"

 

But I believe this is something expected as even Administrator user cannot make query/update on the master account. But, since we have excluded this user, the all users query should not look for master account, right?

I recall vaguely that master should be added to the excluded users lists in config file.

@Pranav Chugh​ as per the document I have already put this user in the ignore list in the GlobalConfig.yml. I believe you are saying about this config file only.

L0 Member

Did you find any resolution to this? I also see that in logs with the master user in the ignore list in globalconfig.

In My case, there was some issue with the global config file. I replaced the same with the file provided by the support which resolved the issue. I think you can use the sample globalconfig file available in the installation folder and upload to the safe without modifying it and give a try.

L0 Member

Thanks that worked for me. I used the gobalconfig.yml sample file which wasn't as extensive but I could always add more users and safes just needed master to not be included.

  • 1070 Views
  • 7 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!