Securely accessing JIRA using OKTA -3rd company Jira board - error messages

[bp_holly_williamson]

My company is using OKTA to log into JIRA.  One of our consultants has given several members access to JIRA and we are having access issues.  One error message our users are getting when trying to access the JIRA board of the consulting company is "Upstream connect error or disconnect/reset before headers.  Reset reason:  connection termination".  Others are just getting "X@email.com doesn't have access to Jira on X.atlassian.net".  the consultant has tried deleting these users and adding them back but this does not resolve the issue.  Most people have no issue, but we have a handful that are receiving one or the other of these 2 messages.

Any help is appreciated.

[Marc - Devoteam]

Hi @bp_holly_williamson 

Welcome to the community.

This is related to the access on the external Jira, are members granted a license and granted access to the required project?

[bp_holly_williamson]

Yes.  Our internal IT team adds the team members to the OKTA group and we have licenses that are allocated.  The admin on the external Jira board is providing access to the required project.  I double check when the team member reaches out to me that I can see their email in the jira group on the project board.

[Marc - Devoteam]

Hi @bp_holly_williamson 

What is the relation to your company okta and licenses (in Jira?) and the external Jira?

If you also have Jira and you grant your users a license will not mean, if this other Jira is a different instance that you have rights there, you will if added to that Jira, you will still need a license on that instance.

This would need to be granted by someone on that instance.

Is this "external" instance linked to your Okta?