The status Is Connected but ind accessible?

Learn about link access rules:

Regardless of OAuth(impersonation) or Oauth, if you want to access data from one end of the app to the other, you must confirm which user at the other end is accessing the data. 

Authentication under OAuth(impersonation) automatically matches the user names of applications at both ends. For example, if the current login user of configuration is "kaifa1", when accessing JIRA data through the application link, the remote JIRA end will match the temporary token granted by "kaifa1" user, and use the data that can be accessed by JIRA "kaifa1" user If there is no "kiafa1" user in the JIRA side, the user will not have access to the JIRA identity. As a result, the conference will be anonymous without identity and can not access any data (OAuth(impersonation));

The problem that the OAuth side can not match the user can be avoided to some extent. Because the real access token is needed, it will not automatically match to get the temporary token. Therefore, your user must go to the remote end of the application to authorize the OAuth of the remote end user.

Open

Open

Scenario 1:

The outgoing and incoming methods of links are OAuth (impersonation), but there is no currently logged in user at the remote end. Take the case of "kaifa1" in the configuration and no "kaifa1" in the JIRA side, the problem of anonymity and no identity will occur in the configuration access and no data can be accessed.

Scenario 2:

The link comes out and is passed in as Oauth, but the current user does not access the token Oauth on the remote side, causing the problem of no token anonymity and no access to any data.

Scenario 3:

The way of outgoing and incoming links is OAuth, but the user who is given access token OAuth by the current user at the remote end is deleted, which leads to the problem of anonymity and no access to any data.