ID1044 An encrypted security token was received at the relying partywhich could not be decrypted

YSOD:
ID1044 An encrypted security token was received at the relying party which could not be decrypted. Configure the relying party with a suitable decryption certificate. Current relying party decryption certificate info:

This error was happening because I went a little-overboard and fancy with the tokens. I set up local client keys and symmetric keys and every possible key that there was. Well, it was too much. I stripped all of that back to only use https and nothing on top of it, and things just worked better.

Solution: 1) Keep it simple. 2) Start out by getting the simplest scenario to work and then add complexity on top of a working concept. It is just much easier to isolate a problem when you are certain that most of it works and there is very little that has changed since the last time it worked.

Advertisements

About Tim Golisch

I'm a geek. I do geeky things.
This entry was posted in Errors, Lessons Learned and tagged . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s