Skip to main content

ello,

I am trying to use a Python script to get a list of our users via the SCIM API.

I am facing a persistent issue. When I generate a new SCIM bearer token, it either fails authentication entirely (returns zero users) or it successfully fetches the user list but is missing the crucial license and role data (urn:ietf:params:scim:schemas:extension:lucid:1.0:User).

I have confirmed my script is correct and have regenerated the token more than 5 times. The problem is with the permissions being granted to the token itself. Our SCIM admin page does not have any settings for "Attribute Mapping" to fix this.

Can you please urgently check our account's backend SCIM configuration and ensure that any new token I generate has full read permissions for all user attributes, including the lucid:1.0:User extension?

Thank you.

@yaswanth I understand the confusion - though what you’re seeing is expected with Lucid’s SCIM implementation.

The available schemas can be confirmed via the /Schemas endpoint - you’ll see:

  • urn:ietf:params:scim:schemas:core:2.0:User
  • urn:ietf:params:scim:schemas:core:2.0:Group

  • urn:ietf:params:scim:schemas:extension:enterprise:2.0:User (department attribute only)

More details can be found in Lucid’s SCIM API documentation.

If you’ve configured your account to have licensing assigned at the organizational group level rather than the individual user level, you can infer license status based on group membership in the /Users response - users belonging to a licensed organizational group are licensed.

There isn’t a public SCIM endpoint that returns per-user license metadata. For visibility into which groups are licensed, you can reference the Admin Panel › Groups › Organizational groups page, or query /Groups via SCIM to correlate membership.

Please let me know if you have any specific questions!