By: Georges Duyahourt user 13 Oct 2020 at 3:16 p.m. CDT

3 Responses
Georges Duyahourt gravatar
I recently updated Gluu from v4.1 to v4.2 : it broke my application because Gluu 4.2 does not expose **/.well-known/scim-configuration** endpoint anymore. This causes the [scim client library for node]( - provided by your team - to fail when trying to initialize, because it cannot discover Gluu SCIM config anymore. I don't know if the removal of this endpoint is a bug or a feature, but I could not find the endpoint for scim-configuration anywhere in oxauth, oxtrust, scim or nginx container (I use docker version on Debian). As a workaround I forked the node library and hardcoded SCIM endpoints, but this does not seems like a long term solution. I also opened an issue in the Github of the node library : Could you give me a hint of the best way to solve this problem ? Thanks

By Michael Schwartz Account Admin 13 Oct 2020 at 3:22 p.m. CDT

Michael Schwartz gravatar
If it's not there it's a bug in the release.

By Jose Gonzalez staff 14 Oct 2020 at 7:51 a.m. CDT

Jose Gonzalez gravatar
Not a bug per se. Endpoint ` /.well-known/scim-configuration` is non-normative and all service metadata is found in already existing endpoints `/ResourceTypes` and `/ServiceProviderConfig` part of "Service Provider Configuration Endpoints" Sect 4 RFC 7644. Georges, I'm going to reopen the github issue and get someone update the Node code.

By Jose Gonzalez staff 17 Oct 2020 at 3:13 p.m. CDT

Jose Gonzalez gravatar
The issue has been fixed and we are awaiting the update of the NPM package (issue #5)