You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I foolishly created a token for graph.microsoft.com instead of graph.windows.net. Running roadrecon gather yielded a large number of 401 errors without an obvious cause:
Error 401 for URL https://graph.windows.net/<id>/applications?api-version=1.61-internal&$select=keyCredentials,objectId
Further debugging showed the error as Authentication_MissingOrMalformed, which was confusing because the requests contained an auth token.
{"odata.error":{"code":"Authentication_MissingOrMalformed","codeForMetrics":"Authentication_MissingOrMalformed","message":{"lang":"en","value":"Access Token missing or malformed."}}}
It took me longer than I'd like to admit to realize my mistake.
Proposed Solution
I have a could ideas to avoid wasting time and sending extraneous requests with an 'invalid' token:
Add a sanity check in run that the token is for graph.windows.net
Update dump_object (or somewhere more appropriate) to treat 401 as a fatal error and cease enumeration.
The text was updated successfully, but these errors were encountered:
Description
I foolishly created a token for
graph.microsoft.com
instead ofgraph.windows.net
. Runningroadrecon gather
yielded a large number of 401 errors without an obvious cause:Further debugging showed the error as
Authentication_MissingOrMalformed
, which was confusing because the requests contained an auth token.It took me longer than I'd like to admit to realize my mistake.
Proposed Solution
I have a could ideas to avoid wasting time and sending extraneous requests with an 'invalid' token:
run
that the token is forgraph.windows.net
dump_object
(or somewhere more appropriate) to treat 401 as a fatal error and cease enumeration.The text was updated successfully, but these errors were encountered: