Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WsFederation Token Encryption (Certificate) #966

Closed
Tratcher opened this issue Jun 19, 2018 · 5 comments
Closed

WsFederation Token Encryption (Certificate) #966

Tratcher opened this issue Jun 19, 2018 · 5 comments
Labels
Customer reported Indicates issue was opened by customer Investigate We are not quite sure what the issue is. P1 More important, prioritize highly

Comments

@Tratcher
Copy link
Contributor

From @qubicaamf on June 19, 2018 8:44

Hi,
As you can read from WsFederation authentication doc:

Microsoft.AspNetCore.Authentication.WsFederation lacks support for token encryption, so don't configure a token encryption certificate...

We need this feature because of Signle-Sing-On auth system, that we want to implement in ours public web apps (Azure App Services working as relying party-trust in our scenario) and other internal (web based) products.

Do you have any plan to add this feature?

Copied from original issue: aspnet/Security#1785

@brentschmaltz
Copy link
Member

@Tratcher what token types are you looking for encryption support?
We support JSON (JWE), are you looking for SAML2?

@brentschmaltz brentschmaltz added P1 More important, prioritize highly Customer reported Indicates issue was opened by customer Investigate We are not quite sure what the issue is. labels Jul 1, 2018
@Tratcher
Copy link
Contributor Author

Tratcher commented Jul 5, 2018

Not I, ask @qubicaamf.

@brentschmaltz
Copy link
Member

@qubicaamf what token types are you looking for encryption support?
We support JSON (JWE), are you looking for SAML2?

@qubicaamf
Copy link

Hi @brentschmaltz, yes we are looking for SAML2.

@brentschmaltz
Copy link
Member

@qubicaamf @Tratcher see #734

Hopefully this makes it into 5.2.5, Aug 10th.
If not Sept / October.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Customer reported Indicates issue was opened by customer Investigate We are not quite sure what the issue is. P1 More important, prioritize highly
Projects
None yet
Development

No branches or pull requests

3 participants