Skip to content

Conversation

sattvikc
Copy link
Collaborator

APIs for SAML support

@sattvikc sattvikc changed the title fix: first draft feat: saml support Sep 12, 2025
@sattvikc sattvikc changed the base branch from master to 5.3 September 15, 2025 07:14
@sattvikc sattvikc self-assigned this Sep 15, 2025
api_spec.yaml Outdated
'500':
$ref: '#/components/responses/500'

/appid-<appId>/<tenantId>/recipe/saml/clients/create:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we are using PUT then we should have it as saml/clients, if we are doing create then it should be POST (and/or rename it to POST createOrUpdate)

Suggested change
/appid-<appId>/<tenantId>/recipe/saml/clients/create:
/appid-<appId>/<tenantId>/recipe/saml/clients:

api_spec.yaml Outdated
Comment on lines 8407 to 8410
accessToken:
type: string
idToken:
type: string
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a bit confusing. I'm guessing this is to reuse as much as possible from the node third-party recipe, but I'd much rather have these as "special providers" on the node level and do it in a single core call (which I think would be the callback)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants