By: Abhishek Jain named 18 Dec 2020 at 12:36 p.m. CST

5 Responses
Abhishek Jain gravatar
##Expected Behaviour SCIM Api should return success response ##Actual Behaviour Hitting URL gluu.xx/identity/restv1/scim/v2/ServiceProviderConfig 1)SCIM api from postman it was returning Error with code 307. 2)From Web navigating to error page ##Logs I also gone through the Gluu doc 4.2 and 3.1.X. There is some configuration response which is returning by below URL without any authentication. If the below API/URL returning response then SCIM can provide response. Steps done From yml file 1) Values.yml file has SCIM enable. Gluu-UI 1) Enable SCIM Support in System Configuration. 2) Navigate to Configuration > JSON Configuration > OxTrust Configuration, scroll down and set the scimTestMode property to true Kubernates get pod gluu-four-jackrabbit-0 1/1 Running 0 3d8h gluu-four-opendj-0 1/1 Running 0 3d8h gluu-four-oxauth-646cf84cd8-6r6mv 1/1 Running 0 3d4h gluu-four-oxshibboleth-0 1/1 Running 0 124m gluu-four-oxtrust-0 1/1 Running 1 3d4h gluu-four-scim-c84b87696-5ng6x 1/1 Running 0 124m Logs 2020-12-17 16:27:17,695 ERROR [qtp1989335500-14] [org.gluu.oxtrust.exception.UncaughtException] ( - Jersey error. RESTEASY003210: Could not find resource for full path: at org.jboss.resteasy.core.registry.SegmentNode.match( ~[resteasy-jaxrs-3.13.0.Final.jar:3.13.0.Final] at org.jboss.resteasy.core.registry.RootNode.match( ~[resteasy-jaxrs-3.13.0.Final.jar:3.13.0.Final] at org.jboss.resteasy.core.registry.RootClassNode.match( ~[resteasy-jaxrs-3.13.0.Final.jar:3.13.0.Final] at org.jboss.resteasy.core.ResourceMethodRegistry.getResourceInvoker( ~[resteasy-jaxrs-3.13.0.Final.jar:3.13.0.Final] at org.jboss.resteasy.core.SynchronousDispatcher.getInvoker( ~[resteasy-jaxrs-3.13.0.Final.jar:3.13.0.Final] at org.jboss.resteasy.core.SynchronousDispatcher.lambda$invoke$4( ~[resteasy-jaxrs-3.13.0.Final.jar:3.13.0.Final] at org.jboss.resteasy.core.SynchronousDispatcher.lambda$preprocess$0( ~[resteasy-jaxrs-3.13.0.Final.jar:3.13.0.Final] at org.jboss.resteasy.core.interception.PreMatchContainerRequestContext.filter( ~[resteasy-jaxrs-3.13.0.Final.jar:3.13.0.Final] at org.jboss.resteasy.core.SynchronousDispatcher.preprocess( ~[resteasy-jaxrs-3.13.0.Final.jar:3.13.0.Final] Can you please help me to get response from SCIM API. Also let me know if I missed any configuration. Note: Previously we were using Gluu 3.1.6 . We were successfully able to get response from SCIM, using Returning response

By Jose Gonzalez staff 18 Dec 2020 at 1:28 p.m. CST

Jose Gonzalez gravatar
Hi there, A missing route?. See

By Abhishek Jain named 21 Dec 2020 at 8:12 a.m. CST

Abhishek Jain gravatar
Refer to We already have scim running in pods. for "scim" kubectl get ingress NAME gluu-four-nginx-ingress-base gluu-four-nginx-ingress-casa gluu-four-nginx-ingress-fido2-configuration gluu-four-nginx-ingress-gluu gluu-four-nginx-ingress-gluu-scim gluu-four-nginx-ingress-openid-config gluu-four-nginx-ingress-scim-config gluu-four-nginx-ingress-stateful .... ...... But still the same problem as above.

By Jose Gonzalez staff 21 Dec 2020 at 9:33 a.m. CST

Jose Gonzalez gravatar
maybe @Mohammad.Abudayyeh can help here...

By Mohammad Abudayyeh staff 22 Dec 2020 at 1:04 a.m. CST

Mohammad Abudayyeh gravatar
Yes @Jose.Gonzalez. We resolved this issue over a call on a different issue yesterday 21-Dec-2020. They were missing the `scim` part from the endpoints. I believe this issue can be closed. The docs should be updated to include a how to or maybe a note about adding `/scim`.

By Jose Gonzalez staff 23 Dec 2020 at 9:17 a.m. CST

Jose Gonzalez gravatar
ok, docs will be updated soon. Thank you.