Skip to content

Conversation

@JoshLozensky
Copy link
Contributor

@JoshLozensky JoshLozensky commented Jan 30, 2025

This PR adds extensibility for customers to be able to define their own signed assertion providers. The integration test in \tests\E2E Tests\CustomSignedAssertionProviderTests\CustomSignedAssertionProviderExtensibilityTests.cs has an example of the sort of work a customer would need to do in order to use this functionality.

Fixes #3220

@github-actions

This comment was marked as resolved.

@github-actions

This comment was marked as resolved.

Copy link
Collaborator

@jmprieur jmprieur left a comment

Choose a reason for hiding this comment

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

Good start
I left some questions/comments. I'm puzzled by the exceptions.

@github-actions

This comment was marked as resolved.

@JoshLozensky
Copy link
Contributor Author

Good start I left some questions/comments. I'm puzzled by the exceptions.

I mistook "log a new error" from the spec for throw a new exception

@github-actions

This comment was marked as resolved.

@jmprieur
Copy link
Collaborator

jmprieur commented Feb 3, 2025

Let's have an aka.ms link for the error messages for this feature.
https://aka.ms/msidweb/ms-id-web/custom-signed-assertion-providers, that will link to the wiki page

This was referenced Oct 31, 2025
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.

Expose credential loader extensibility to support custom signed assertion providers

5 participants