AADSTS50107: The requested federation realm object <URL> does not exist
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 426
- Forks
- 70
- PR merge metrics
- No merged PRs in 30d
Description
Running ADFSpoof generates the token as expected but when replacing the 'wresult' parameter in an authentication flow (through burp) I keep getting the "AADSTS50107: The requested federation realm object does not exist" error.
The generated token look nearly identical to the one that is created by ADFS - I saw another issue that stated that now you have to go through the entire login process as the login.srf request should contain all the headers to the server as opposed to just sending a request with the token (like on the video from RT19) so I wonder if anything else was change that causes the error I am experiencing?
Informative:
- key is converted to binary format
- signing token is decoded with base64 and saved to a file (it looks like the expected binary format as well)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source files or tests are named. Start by reproducing the ADFSpoof token flow and comparing the generated token, wresult, and login.srf request with a working ADFS flow, including the headers mentioned in the report; done means the authentication flow succeeds without AADSTS50107.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- authentication, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100