Hi @aking43 You can add an auth login component! This will allow end users of the app to initiate the auth process as needed.
Thanks for the feedback @plwolfe and it definitely makes sense that this wasn't a stable solution. 
We take stability very seriously, so I do want to at least share some additional context. We looped in our on-call engineering team internally when the "Client must be authenticated to access this resource." errors started to come in. It was a little tricky to troubleshoot as the errors were somewhat inconsistent, and the timing of them also coincided with a Jira incident. It did turn out to be a regression that could be solved by manually modifying the domains.
As we continued to monitor for these errors, we also saw reports of the share credentials toggle not working. This behavior is definitely concerning, but it seems to be separate from the "Client must be authenticated to access this resource" regression as we hadn't made a recent change to this code. This is now fixed, so you can share credentials using the Jira integration