Skip to main content

Windows Identity Foundation: SSO issue when browsing from one subsite to another

Last week I had some fun investigating a WIF issue. A colleague came to me and explained the following situation:

I have 2 sites under the same domain each configured as a separate application in IIS with their own applicationpool. Site 1 is available at my.domain.name/Site1. The other site is available at my.domain.name/Portal/Site2. When I login to site 1 through ADFS everything is ok. Then I go to site 2 where I also login. When I then move back to Site 1, I get the following error message:

The input is not a valid Base-64 string as it contains a non-base 64 character, more than two padding characters, or an illegal character among the padding characters.

clip_image001

When I investigated the issue, I noticed that the “same” FedAuth cookie was issued twice, once scoped to my.domain.name/Site1, once scoped to the root domain my.domain.name. When browsing back to Site1, WIF get both cookies(as both apply to the target domain). However as both cookies are issued for different websites, combining them results in an invalid cookie, explaining the error message above.

To solve this we had to change the WIF configuration to scope the cookie correctly:

The original config:

<system.identityModel.services>

    <federationConfiguration>

      <cookieHandler requireSsl="true" />

      <wsFederation passiveRedirectEnabled="false" issuer="https://adfs2/adfs/ls/" realm="https://my.domain.name/site1/" requireHttps="true" />

    </federationConfiguration>

</system.identityModel.services>

The updated config:

<system.identityModel.services>

    <federationConfiguration>

      <cookieHandler path="/" requireSsl="true" />

      <wsFederation passiveRedirectEnabled="false" issuer="https://adfs2/adfs/ls/" realm="https://my.domain.name/site1/" requireHttps="true" />

    </federationConfiguration>

</system.identityModel.services>

After doing that, we got an other error instead:

ID4291: The security token ‘System.IdentityModel.Tokens.SessionSecurityToken’ is not scoped to the current endpoint.

clip_image001[5]

This error is caused by the fact that both sites are using a different application pool.  To solve this second error, there are 2 possible solutions:

Solution 1

Run both sites using the same application pool.

Solution 2

Update your WIF configuration to use the MachineKeySessionSecurityTokenHandler instead of the default SessionSecurityTokenHandler:

<system.identityModel>

  <identityConfiguration>

    <securityTokenHandlers>

     <remove type="System.IdentityModel.Tokens.SessionSecurityTokenHandler, System.IdentityModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" />

      <add type="System.IdentityModel.Services.Tokens.MachineKeySessionSecurityTokenHandler, System.IdentityModel.Services, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" />

</securityTokenHandlers>

  </identityConfiguration>

</system.identityModel>

Popular posts from this blog

DevToys–A swiss army knife for developers

As a developer there are a lot of small tasks you need to do as part of your coding, debugging and testing activities.  DevToys is an offline windows app that tries to help you with these tasks. Instead of using different websites you get a fully offline experience offering help for a large list of tasks. Many tools are available. Here is the current list: Converters JSON <> YAML Timestamp Number Base Cron Parser Encoders / Decoders HTML URL Base64 Text & Image GZip JWT Decoder Formatters JSON SQL XML Generators Hash (MD5, SHA1, SHA256, SHA512) UUID 1 and 4 Lorem Ipsum Checksum Text Escape / Unescape Inspector & Case Converter Regex Tester Text Comparer XML Validator Markdown Preview Graphic Color B

Help! I accidently enabled HSTS–on localhost

I ran into an issue after accidently enabling HSTS for a website on localhost. This was not an issue for the original website that was running in IIS and had a certificate configured. But when I tried to run an Angular app a little bit later on http://localhost:4200 the browser redirected me immediately to https://localhost . Whoops! That was not what I wanted in this case. To fix it, you need to go the network settings of your browser, there are available at: chrome://net-internals/#hsts edge://net-internals/#hsts brave://net-internals/#hsts Enter ‘localhost’ in the domain textbox under the Delete domain security policies section and hit Delete . That should do the trick…

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.