Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 309 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
BC Custom connector with Oauth2.0. Authentication issues
RatedZer0
Member Posts: 7
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,
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,
0
Answers
I add an image of the message that users get when trying to use the app the first time in a while.
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.