Forum Discussion

JBFF's avatar
JBFF
Regular Visitor
6 years ago
Solved

User Suddenly Cannot log into PBI

One of our clients can no longer log in. She goes through the normal motions of logging in to our client report portal through the provided app.   When she tries to log in, she immediately gets thr...
  • JBFF's avatar
    6 years ago

    Apologies for the late update on this one. Clients were very slow to respond.

     

    After a lengthy investigation by microsoft, they discovered that our client's tenant no longer had a valid security token...meaning they completely forgot to renew their security certificate for their tenant. *facepalm*

     

    Issue was completely on the client's end. Once they update their certificate, our client was able to log in without any issues.

     

    For reference, here's what Microsoft found: Key takaway is "Unable to verify token signature"

     

    What's happening here is: Customer is inviting user [Email redacted]. When this user tries to redeem the invitation, they hit SAML validation error.

    AADSTSXXXXXX: Unable to verify token signature. No trusted realm was found with identifier 'https://accounts.google.com/o/saml2?idpid=XXXXXXX' 

    But if we look up this user [Email redacted] in MSODS, turns out this is a valid user on an Azure AD tenant: Tenant-ID

     

    _ObjectClass (1): User _ObjectId (1): User-ID UserPrincipalName (1): [Email redacted]  WindowsLiveNetId (1): XXXXXXXXXXXXXXXXX

    Now the verified domain XXXXXXXX.com is federated with GSuite.

     

    So, it looks like:

    Customer inviting an account through organizational relationship with GSuite but the account itself is part of an Azure AD federated domain federated with G Suite in the first place.

    Mr. XXXXX given the above scenario, could you help confirm if this invite process would work?