How to access `group.*` events (e.g. `group.created`) in the context of Inbound SCIM

Hi everyone

We are integrating with customers who want to provision users via Inbound SCIM into Auth0. Our goal is to react to provisioning changes so that we can keep the users in our app up to date.

However, from reading the docs, I can see that

  • Auth0 supports inbound user provisioning via SCIM
  • Auth0 does not support a /Groups endpoint for inbound SCIM
  • Additional attributes (like group information) may be synced via login or metadata
  • Auth0 does not support outbound SCIM

Given Auth0 doesn’t support outbound SCIM, I have been looking into Event Streams as a way to update our app with the relevant events. This looked promising at first but then I realised all the event streams only allow you to subscribe to organisation and user based events. This would get us part of the way there with the user events but not the whole way as we would need group info as well.

I was about to scrap that idea but then spotted the groups events in the Auth0 Events docs. The docs contain all the user and organisation events that I can subscribe to via the UI but also these group events that I think would work really well for us to update our app.

Are group.* events actually available to customers today and if so, how do I get access to them ? Also, given that Inbound SCIM does not support /Groups, is there any supported way to detect or react to group-like changes via events

Any help would be greatly appreciated.

Cheers

Lee

Hi @leeturnerwm

Welcome to the Auth0 Community!

I fully understand your current use-case for implementing outbound SCIM and while currently Auth0 does not support this feature, we do have some good news : looking at our Auth0 Changelog, we can see that Inbound SCIM Groups for Enterprise Connections is now in Limited Early Access has been recently added, on the 30th of Jan. This indicates a strong development towards implementation and according to the doc, it is possible to reach out to your Account Owner after filling out the form to request to activation of this feature for specific use-cases.

We also have a couple of Feature Requests on this idea that you can vote on, which would help our Product Team ( they have visibility over all Feature Requests ) drive more interest and engagement:

Returning to your use-case, we currently do not seem to have an official way of handling the flow or a workaround, based on this topic Outbound SCIM configuration, we recommend reaching out to our Professional Services team for a custom Outbound SCIM solution in order to ensure security and effectiveness.

I hope this provided some useful information for you, please do not hesitate to reach out to us for any other issues or requests, we’ll be glad to help out!

Have a great one,
Gerald