thinktecture-ident-server

We've setup federated security using ThinkTecture server. When a user wishes to access a particular URL, they get redirected to the Identity Provider Server (IDP), they login, get authenticated. Then, the IDP server will redirect the user back to the "Redirect URL" specified in the configuration for that Relying Party. Instead, I want it to be redirected to the originally requested URL. Is this possible? I've read a little about the wreply parameter, but not sure how I use this and intercept the authentication levels calls on the original web server, before the redirect. Update I've realised

I'm using the Thinktecture.IdentityServer.v2 app to perform SSO for a couple of internal apps but would like to customize the login page for each application to have a smoother user experience. I can't seem to find a way to do that. Can the login page be customized depending on the source application from where the client is comming? "I can't seem to find a way to do that." - How hard have you tried? ;) The RP has the extra data fields - so you can hang like a CSS name off the RP in the registration database. Further you can get to that RP data from the signin page - quoting the comment in

I implemented authentication and authorization using Identity server 4 with OIDC to allow clients accessing our application to get the necessary tokens to access our resource server (web APIs). This is the current architecture : Identity Server 4 using my custom DB to authenticate users Resource APIs (ASP.NET Core) Angular 2 front end I need to implement SSO, where users from other systems will pass SAML2 assertions from their identity providers to allow them to access our resource APIs without logging in to our application. I have some confusion about where this step will happen, and what

I'm very new to the identity management world, so please spare me. :) What I would like to do, is to have multiple client (MVC) applications that talk to a single Web API application to authenticate their users against. In that Web API application, I would like to use ASP.NET Identity to talk to a database with users. That way, I could use SSO for the client applications (I guess). Does that make sense? Could someone help me on my way to implement this (links are also welcome of course)? I don't know if IdentityServer could help me with what I want? And as a side question: when I could

I'm having some dramas making a call against a ServiceStack REST service which I've secured with an out of the box IdentityServer STS. I'm making an AJAX call against the REST endpoint, and I'm not sure how one might setup a logon procedure to get a security token to pass. The REST endpoint is on a different domain than the website making the call. The info that I've found so far all seems to revolve around the procedure where the client makes a call to the secured resource gets a 302 redirect to the identityserver logon page, then after successful authentication gets a 302 redirect to either

Secure 2 different web applications with one identify service Identity Service: Thinktecture Identity Service V2 Application 1: Asp.net MVC 5 application Application 2: Asp.net Web API application The above Applcation 1 and Application 2 are different projects and hosted in different servers. Now my scenarios are 1. Want to secure Application 1 with Identity Service. 2. Want to secure Application 2 with Identity Service. Use case 1: If user access Application 1 it should redirect to identity service login page, once I entered the credentials and login in to application 1, the same token allow