docs: outbound scim event stream action#1464
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
b7ff8af to
43e13a5
Compare
Summary
Redirects per inputRedirects in main/docs/customize/events/event-types.mdx
|
| * A downstream SCIM 2.0 endpoint that accepts `POST`, `GET`, `PUT`, and `DELETE` on `/Users`. | ||
|
|
||
| * A SCIM server. |
There was a problem hiding this comment.
[nit] think it's worth merging the endpoint with the server bullet? or maybe list the server before the endpoints?
|
|
||
| * The SCIM server must support an `externalId eq` filter. | ||
|
|
||
| If the server rejects the `externalId eq` filter, the Action falls back to a `userName` filter, which matches on name and therefore cannot track an email change. |
There was a problem hiding this comment.
this could be friday brain, but is this saying it matches on the stored userName value, which is the
pre-change email, so it can't locate a user whose email just changed?
feel free to disregard, but maybe something like this could clear it up:
"If the server rejects the externalId eq filter, the Action falls back to a userName filter. Because userName defaults to the user's email address, the stored value is the pre-change email. Therefore, a lookup by the new email will not find the record, and email changes cannot be tracked."
Co-authored-by: Nick Gagliardi <133918568+nick-gagliardi@users.noreply.github.com>
Description
docs for the new action template for outbound SCIM with event streams.
also modernizes the section landing page while i was in there:
launch is early next week so please do not merge :)
References
DOCS-5543
Checklist
CONTRIBUTING.md.