Changing AD Group Authorisers not taking effect quickly

  • 23 January 2015
  • 2 replies
  • 6 views
S
Userlevel 3
Badge +16

Hi,

 

I use Workflows to send email Approvals to Authorisers.

 

My K2 Studio Workflow using AD Security Groups to send the Approval to.

If I add or remove a user, this is not being reflected in the form.

 

For Example: In my AD Group, there were 2 users, I removed one user from it. Then i ran the form and submitted it. The workflow kicks in and send the Approval to the Approver Group, but the two users are still getting the approval (even though i deleted one of the users)

 

If this a synchronisation issue? The workflow simply sends the Approval to the AD Group (has resolve roles and groups to users) but why isn't it checking the AD group to see who is the "current" members before the approval is sent? It still sends the approval to both approvers.

 

I have waited for an hour and still it sends the approval to both users. The only way i could get this to go to one user (as in current membership) is to re-deploy the workflow.

 

Any ideas what is going on?

 

If I send an email to the Group Email Address, that works fine and is instant and only sends it to one user. So why the problem with k2 sending the Approval using the AD Group? Is it being cached?

 

Anyone else had this issue?

 

Thanks,

2 replies

T
Badge +10

It is being cached.  The default I believe is 8 hours. 

 

Take a look at the following which describes how this works

http://help.k2.com/onlinehelp/k2blackpearl/icg/current/webframe.html#tweaking_identity_cache_performance_for_the_k2_server.html

 

You can refresh the cache but it does require running a SQL script:

http://help.k2.com/onlinehelp/k2blackpearl/icg/current/webframe.html#refresh_usermanager_cache.html

 

T
Userlevel 5
Badge +18

You can also use the ForceIdentityRefresh Tool from:


 


http://community.k2.com/t5/General-K2-Utilities/Force-Identity-Service-Refresh/ba-p/74061


 


To expire the memberships property to that group.  And then use the Smartobject Service Tester Tool > Smartobject Explorer > All SmartObjects > UMUser > Get Group Users method; (execute this method at least twice or more until you see the change in membership, indicating that it is cached):


 


13232i04211CB0C162AF3E.png


 


 All of these expiring and updating usually happen automatically with the default settings; the steps demonstrated above is another way to update and cache it right away if needed.

Reply


View our Community Site Map

Nintex Community Sitemap
Terms & ConditionsCookie settings