[ALM Accelerator - BUG]: Response data should be valid JSON object

[ryanhodgson1]

Describe the issue

A common error that people get is when the token refreshes for the custom azure devops connection used for ALM and then they get this message:

This can be resolved if i add them as admin to the ALM environment and they manually delete the custom connection like this:

Is there a way to add a button in ALM itself to refresh this connection so i dont have to add people as admin in the environment?

Expected Behavior

For the refresh to not cause an error or have a way to manually refresh it

What component are you experiencing the issue with?

ALM Accelerator Canvas App

What solution version are you using?

1.0.20230606.1

Steps To Reproduce

No response

Anything else?

No response

AB#575

AB#1645

[mikefactorial]

@ryanhodgson1 are users not able to see/delete their own connections in the ALM Accelerator environment without admin permissions? That seems odd. Can't say I've ever really looked into it but would have assumed they could...or I guess maybe they need at least maker permissions?

Anyway, let me see what our options are here.

[ryanhodgson1]

Thanks @mikefactorial Ill give environment maker a try and see if that works for the next person that has the issue, but will be nice if there was a way to force ALM to get the new token from the app UI itself

[SAEED2ALAHMARI]

microsoft/coe-starter-kit] [ALM Accelerator - BUG]: failed pipeline on Set Dataverse AAD Group Teams (Issue #4991)

How do I get help with this Issue? https://github.com/microsoft/coe-starter-kit/issues/4991#event-9807014852

[RajeevPentyala]

microsoft/coe-starter-kit] [ALM Accelerator - BUG]: failed pipeline on Set Dataverse AAD Group Teams (Issue #4991)

How do I get help with this Issue? https://github.com/microsoft/coe-starter-kit/issues/4991#event-9807014852

@SAEED2ALAHMARI Regarding the https://github.com/microsoft/coe-starter-kit/issues/4991, since we did not receive a response from you regarding the requested details, we have proceeded to close the current ticket. If the issue persists or you have any further concerns, we kindly request you to log a new ticket with the latest details. Thank you for your understanding.

[mikefactorial]

@ryanhodgson1 is this still an issue? Been trying to research it for a while but haven't found much in the way of a fix or been able to replicate but I guess it could be because I'm using the Accelerator on a daily basis and maybe doesn't have time to timeout? Not sure...

[ryanhodgson1]

Hey @mikefactorial

Yeah still an issue, i get a message from someone that gets the error once every few days.

[ryanhodgson1]

Hey @mikefactorial I am moving on from my current role so tagging in Nomer and Jhiggy below to follow up on these outstanding issues after im gone, thanks.

@agent-roman @abesamisj FYI