Home/ Questions/Q 7724627
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-01T04:44:14+00:00

I have a requirement to pass credentials from one Microsoft .NET Web Application to

  • 0

I have a requirement to pass credentials from one Microsoft .NET Web Application to another via Single-Sign-On at the Browser. I was hoping to utilize Windows Azure (ACS) as my Secure Token Service along with a Facebook/Open Id as the Issuing Authority for the claim for authentication purposes only.

Does anyone know how I achieve ‘Federated claims-based authentication and single sign-on’ across different .NET Web Application?

Note the two different Web Application are hosted in different data centers (not the cloud), credentials need to flow via the browser, is this achievable via the claim and a cookie (if so how)?

Cheers

*Update
e.g. User logs into Application A via ACS, they then click a button on App A which redirects them to App B (partner/3rd party site)

FYI – I don’t think I will have access to change Application B (Partner Site), Application A yes…

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    What you’re describing here is a hybrid scenario that works perfectly with the Windows Azure Access Control Service. And it doesn’t matter if your application is on-premise or in the cloud. Basically your applications will simply need to use ACS as identity provider (right click on your projects, add STS reference). Once you’ve done that, the following will be possible:

    1. User browses to application1.com
    2. Authentication is required. application1.com redirects to the ACS ‘login page’ (where you can choose an identity provider) or lists all available identity providers.
    3. User chooses to use Windows Live
    4. User is redirected to login.live.com where he can enter his email address + password. He chooses to save the password and stay connected.
    5. User is redirected to ACS with some claims. ACS redirects again with some claims to application1.com
    6. User is authenticated in application1.com and his claims are available in the application.
    7. User connects to application2.com
    8. Authentication is required. application2.com redirects to the ACS ‘login page’ (where you can choose an identity provider) or lists all available identity providers.
    9. User chooses to use Windows Live
    10. User was already authenticated in Windows Live before! And login.live.com redirects him immediately to ACS with some claims
    11. ACS redirects again with some claims to application2.com
    12. User is authenticated in application2.com and his claims are available in the application.

    Hope this helps.

    Sandrino

    • 0