BC Custom connector with Oauth2.0. Authentication issues

RatedZer0
RatedZer0 Member Posts: 7
edited 2022-02-22 in NAV Three Tier
We created an API connector to a PowerApp which works fine, but after some time (ccouple of hours) an error appears saying that the connection needs to be repaired which makes us relog in with the user for the connector.

This is a problem because not all users have the account for the connector.

We have tried giving permissions to the Oath2.0 connection, but it keeps giving the issue to the users.

Does anyone have any idea on how to avoid this reauthentication demanded by the connector every couple of hours? We'll need it to not ask at all or the maximum time we could get.

Thanks in advance!

Sincerely,

Answers

  • RatedZer0
    RatedZer0 Member Posts: 7
    RatedZer0 wrote: »
    We created an API connector to a PowerApp which works fine, but after some time (ccouple of hours) an error appears saying that the connection needs to be repaired which makes us relog in with the user for the connector.

    This is a problem because not all users have the account for the connector.

    We have tried giving permissions to the Oath2.0 connection, but it keeps giving the issue to the users.

    Does anyone have any idea on how to avoid this reauthentication demanded by the connector every couple of hours? We'll need it to not ask at all or the maximum time we could get.

    Thanks in advance!

    Sincerely,

    I add an image of the message that users get when trying to use the app the first time in a while.

    m09b4qplh6h2.png

    It comes to say: "The app needs your permission to use the next:" and then the connector with a "Repair connection" issue. If we click on the issue it gets repaired and works fine, but we need to avoid this message at first.

Categories