Skip to main content

Suggest an Idea

Vote for your favorite Qlik product ideas and add your own suggestions.

Sharepoint connection uppdate token

AronC
Partner - Creator II
Partner - Creator II

Sharepoint connection uppdate token

Today when you set up a connection to Sharepoint it is only valid for 90 days.  After 90 days if you don't manually refresh the data-connection you get the error "The refresh token has expired due to inactivity".  The connection is active though and retrieves data everyday. But the refresh-token hasn't been updated. 

The limit of 90 days is set by Microsoft, but it should be possible to make an update of token automatically without the need for a user to manually update the data-connection.

My suggestion is that the Sharepoint-data connection handles this.

Regards,

Aron

Tags (2)
6 Comments
paulcalvet
Partner - Specialist
Partner - Specialist

it's a must have !

Managing connections with this restriction is very annoying, non-expert users do not understand the error message.

Lachlan
Contributor II
Contributor II

Our organisation has several hundred Sharepoint subsites, each of which has a different connector. Having to manually go in and reauthenticate each one every 90 days is time consuming and inefficient, in a tool which is automated in almost every other sense.

paulcalvet
Partner - Specialist
Partner - Specialist

Hello @Lachlan , this feature is available since yesterday.

paulcalvet_0-1669885868519.png

Meghann_MacDonald

Hi, this idea has also been submitted here and is being tracked: https://community.qlik.com/t5/Suggest-an-Idea/Automation-of-updating-authentication-token-in-Qlik-Of...

Meghann

Status changed to: Closed - Duplicate
AronC
Partner - Creator II
Partner - Creator II

@Meghann_MacDonald This has already been implemented.  Why is it still beeing commented? This thread was also the first in the subject and should not be considered a duplicate.

 

Meghann_MacDonald

Hi @AronC , I’m cleaning up some of the Ideation forum to make sure nothing is missed. The only reason we closed this as a duplicate (as opposed to the other) is because the product manager  P-O already updated the status in the other idea as “Partially Delivered” - so rather than marking both ideas as delivered, we merge them. Then the likes & comments from both ideas are counted and it is considered Partially Delivered.