KeySafe entry token refresh failing.

[JamesGreen]

Was reported that Hornbill was failing to send private messages via Teams with error Session Error from Teams API: Refresh Token Generation Error: The 'resource' request parameter is not supported.

Normally when this happens we revoke access on the Keysafe Entry linked to this and connect again. However when we try connect again we get "Instance endpoint call failed" 

Even tried creating new Keysafe Entry to see if we could start from scratch but also same issue.

Instance endpoint call failed"

[Berto2002]

Impact: none of our iBridge integrations with Teams are working; which includes creating and updating private messages, starting and updating conversations in channels.

 

Error received from Cloud node when attempting to create a new Teams conversation in a channel:

Error: Error from Teams API: InvalidAuthenticationToken: Teams API Error: CompactToken parsing failed with error code: 80049217

 

Error received from Cloud node when attempting to create a new private message to an individual:

Create chat error (no error if blank after colon): Session Error from Teams API: Refresh Token Generation Error: AADSTS901002: The 'resource' request parameter is not supported. Trace ID: 1b86d243-630e-40a9-a965-0402d92b4c00 Correlation ID: 89602aa4-8dad-4293-85da-ba9fa3d52c73 Timestamp: 2023-12-14 08:29:40Z

 

From our side we see this as traffic between Hornbill and Microsoft, and we don't have a point at either end where we can capture it and diagnose.

[Keith Stevenson]

@JamesGreen
We have identified an issue with the generation of new Key Safe items and made a change that should resolve this. Can you try again and confirm 


Kind Regards

Hornbill Cloud Team 

[Adith]

+1
@Keith Stevenson - Had similar issue with Teams integration, tried revoking and reconnecting but getting "Instance endpoint call failed" error.

[Berto2002]

I don't think this is fixed @Keith Stevenson. Colleague should confirm soon.

 

[Keith Stevenson]

@Berto2002
Just to clarify the change made is to specifically fix the ""Instance endpoint call failed" on the creating KeySafe. Not any other issue and it should be this that is tested\confirmed.

Kind Regards

Hornbill Cloud Team 


@Adith
Will make the change to your instance now..  Give it 10 minutes and test again 

Kind Regards

Hornbill Cloud Team 


 

 

[Berto2002]

@Keith Stevenson it still gives the same error when we create a new token in keysafe:

[Adith]

@Keith Stevenson - Still same error for us too. 

[Keith Stevenson]

All,
Thanks for the posts. We are checking the change. 

Kind Regards

Hornbill Cloud Team 

[Berto2002]

Looks like something went wrong on Tuesday afternoon or evening. That's when it looks like we last had a successful Teams update; in case that helps you find a change that has caused this from earlier in the week.

Text of the last update I can see what just before 5pm Tuesday

[Adith]

@Keith Stevenson Any further updates on this ?

[Keith Stevenson]

All
Thanks for the information. We have now replicated and resolved the issue inhouse. This will be part of tomorrows 5AM ESP update .

Kind Regards

Hornbill Cloud Team 

[Keith Stevenson]

All,

The ESP release containing the fix went live this morning and testing shows the issue with Keysafe creation no longer occurs. 

Kind Regards

Hornbill Cloud Team 

[Berto2002]

We have been able to successfully renew the MS Teams token.

[Adith]

Good Morning,
Tried the connection and it is successful for us. Thank you

[Berto2002]

I have just logged a Premier Success Urgent Support ticket since our Teams tokens are not working again. This is what happened earlier in the week.

[Berto2002]

We just renewed the token again and the service was restored.
So the issue appears to be that the Teams iBridge token is dropping-out a short while after a token refresh.