I have a few questions about IdentityServer (I don't know if this is the right place to ask?)
First some background:
Today we're using OpenAM as identity provider, and another OpenAM as a service provider. Our .NET-applications communicate with the service provider using custom-built HttpHandler. The sP redirects to the idP wich is located elsewhere (out of our control). The idP returns a users birthnumber and securitylevel (this is a national service, and every citizen in norway can sign in here). Our sP pass-trough birtnumber and securitylevel-claims from idP to our .NET-application (using built-in functionallity in OpenAm). We also have a custom developed PAP-module(post-authentication-processing-module) developed in Java for OpenAm wich applies some custom attributes to the token from a database before it's returned to our .NET-applications..
What we want:
a central authenticationserver/service located at our company wich can be used by all our future applications.
Use standard .NET-libraries to talk to our central authenticationserver (WIF)
Create a webapplication where users can apply for access, and approve access. Everyone in Norway can log in, but when they try to access an application, they get a form "request permission to this application".
chained authentication on intranet. SSO if employee is at work, and fallback to other login-methods if AD is not available
Use Microsoft-tecnologies as far as possible
Questions:
Have you tested IdentityServer agains OpenAM/OpenSSO?
Does IdentityServer support or plan to support chained authentication? (This is a nice feature in OpenAm). If not, would it be hard to implement?
Does IdentityServer support/plan to support adaptive risk? For example: a user can log in with AD and gets readaccess, but if the user wants to edit he is requested to provide additional login-information (sms, or similar)
What dou you mean when you say that IdentityServer has "Out of the box integration with ASP.NET membership, roles and profile"?
We are currently considering IdentityServer, ADFS2.0, and OpenAM as our serviceprovider/STS. Do you have any thoughts on wich solution would fit our needs?
I've tried to connect to OpenAM using WIF (without success), do you know if anyone has accomplished this before?
You're having a claims-workshop in London at NDC, does it include pizza?
Hi.
I have a few questions about IdentityServer (I don't know if this is the right place to ask?)
First some background: Today we're using OpenAM as identity provider, and another OpenAM as a service provider. Our .NET-applications communicate with the service provider using custom-built HttpHandler. The sP redirects to the idP wich is located elsewhere (out of our control). The idP returns a users birthnumber and securitylevel (this is a national service, and every citizen in norway can sign in here). Our sP pass-trough birtnumber and securitylevel-claims from idP to our .NET-application (using built-in functionallity in OpenAm). We also have a custom developed PAP-module(post-authentication-processing-module) developed in Java for OpenAm wich applies some custom attributes to the token from a database before it's returned to our .NET-applications..
What we want:
Questions:
-Thomas