cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
cl0wn
Level: Powered On

Custom Connector Authentication Expiry Issue

Hi All,

 

I have built a custom connector, to consume some of the endpoints for the microsoft graph, that I wish to use in my flow.

 

I have setup my app registration and have created my custom connector and can use it in my flow... but every hour the flow fails with the message saying that one of my connections, my custom connection, is in a disconnected state.

 

"Broken connections

We have found 1 of your connections in a disconnected state. Would you like to fix them now?"

 

I get the same issue using MS Flow or doing this via a Logic App and Logic App connector.

 

Which makes me think this is related to the appregistration settings?

How do I stop this scenario from happening?

What configuration does MS use to get their connectors working and NOT expiring?

 

My connector is using OAuth 2.0.

 

I have read the following - without coming to a resolution:

https://answers.microsoft.com/en-us/msoffice/forum/msoffice_o365admin-mso_other-mso_o365b/ms-flow-ac...

 

https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-configurable-token-...

 

Any insight and help would be much appreciated

 

Pete

2 ACCEPTED SOLUTIONS

Accepted Solutions
Highlighted
Community Support Team
Community Support Team

Re: Custom Connector Authentication Expiry Issue

Hi @cl0wn ,

 

Thanks for updating.

 

I am not sure how is your Custom API configured, please follow this blog and try again with it:

https://medium.com/capgemini-dynamics-365-team/a-microsoft-flow-custom-connector-step-by-step-from-s...

 

I will try to invite more resources into this issue. I will back to you once I got any updates.

 

Best regards,

Mabel

 

Community Support Team _ Mabel Mao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
cl0wn
Level: Powered On

Re: Custom Connector Authentication Expiry Issue

Hi Mabel,

 

That seems to have worked by following that article. (I'll double confirm over the next couple of days)

 

The only difference betweent the two, was the Identity provider. When I set mine up I had set the connector to use OAuth 2.0 -> Generic Oath 2 as the identity provider.

 

The article you linked to used:

OAuth 2.0 -> Azure Active Directory as the identity provider.

 

Whilst that works is there way to configure the Generic Oauth 2 identity provider timeout settings? I am guessing this is somewhere in AzureAD?

 

Pete

4 REPLIES 4
Community Support Team
Community Support Team

Re: Custom Connector Authentication Expiry Issue

Hi @cl0wn ,

 

Have you enabled MFA while signing in the connection?

 

Have your admins done something in the background that is affecting the refresh requirements so flow’s attempts to refresh fail?

 

I have seen another similar thread, please check it at here:

https://powerusers.microsoft.com/t5/General-Flow-Discussion/Flow-Connections-error-due-to-Credential...

 

Best regards,

Mabel

 

Community Support Team _ Mabel Mao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
cl0wn
Level: Powered On

Re: Custom Connector Authentication Expiry Issue

Hi Mabel,

 

Yes I saw that other post but it hasn't solved anything.

 

I also don't have MFA enabled. This is happening on my organisations tenant as well as my own developer tenant. Netither of those tenants use MFA. Both have exactly the same issue.

 

Pete

Highlighted
Community Support Team
Community Support Team

Re: Custom Connector Authentication Expiry Issue

Hi @cl0wn ,

 

Thanks for updating.

 

I am not sure how is your Custom API configured, please follow this blog and try again with it:

https://medium.com/capgemini-dynamics-365-team/a-microsoft-flow-custom-connector-step-by-step-from-s...

 

I will try to invite more resources into this issue. I will back to you once I got any updates.

 

Best regards,

Mabel

 

Community Support Team _ Mabel Mao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
cl0wn
Level: Powered On

Re: Custom Connector Authentication Expiry Issue

Hi Mabel,

 

That seems to have worked by following that article. (I'll double confirm over the next couple of days)

 

The only difference betweent the two, was the Identity provider. When I set mine up I had set the connector to use OAuth 2.0 -> Generic Oath 2 as the identity provider.

 

The article you linked to used:

OAuth 2.0 -> Azure Active Directory as the identity provider.

 

Whilst that works is there way to configure the Generic Oauth 2 identity provider timeout settings? I am guessing this is somewhere in AzureAD?

 

Pete

>