Hello,
For a while now we've had occasional issues where our SES401 entries don't line up with the role assignments in the other security functions (SES400, MNS410, etc). To rectify this we have to disconnect the user from the role and re-assign it. Unfortunately, sometimes a number of users get impacted and it can be hard to get visibility on everyone who was affected. As well, it can be disruptive for the users, especially in global regions.
The existing solution
Read more...to prevent this is to use the SES990 job. However, our environments are decently large and it takes SES990 hours to finish. Let alone, there is no way to exclude service accounts from the process so they can be in the limbo state for quite a while. Recently it was recommended by Infor that we run SES990 once a month, which would be very difficult for our company to accomplish.
Anyways, I was wondering if anyone else has run into this? Do you have any alternative solutions? Right now I'm thinking of using XtendM3 to create a custom SES990 that could be more targeted but I want to see if anyone else has utilized any other solutions first.
Apologies if there are any problems with the post, it's my first one. Regardless, thanks for any thoughts or input! Show less...
First of all, thanks for all of the responses and I'm glad to hear that I'm not the only one who has bumped into this (or a version of this) problem.
Loretta- Thank you for the reply, I'm glad to hear that running once a month does seem to be effective for preventing the sync issues. Whether we do a custom version or just run the 990 it's good to know that the frequency Infor recommended does indeed work. I'm very hopeful to get to a place where we can Read more...prevent these issues as opposed to being reactive.
Patrick- Thanks for the reply! We have typically seen the issue affect a role that is assigned to multiple users. Then some, but not all, of the users will have a discrepancy in SES401. But agreed with Karen's comment, removing and re-adding does typically resolve the issue- however we can have a decent number of users impacted so I'm hopeful for some alternative solutions as well.
Gavin- Thank you for the suggestion! I have used this before and going forward I think I will use this first, since our problem does seem to mostly impact a single role-program connection when it occurs (though it's different role-program connections each time). Just to clarify on that, the problem will always be a role-program connection, which then downstream impacts a percentage of the users with said role assigned. Thanks for the suggestion and I will definitely be incorporating this in my troubleshooting more.
Marie- Thank you for the suggestion, I have not actually tried to adjust the dates in order to get the sync triggered, but I will going forward!
Karen- Thanks for the response, I'm glad I'm not alone in seeing this problem! And agreed, the process you described is typically how I do resolve the issue as well. The real problem for us on why we need some other solutions is because we support some global offices that unfortunately could (and have) encountered a problem like this while I'm off. Regardless, thank you for the corroboration!
Thanks again everyone for the responses these were both immediately useful and also helpful in knowing it isn't just our system experiencing issues like this! I will make another comment or a new post if there is any update in our long-term solution for prevention. Show less...
Share a Message
Share a Message
Are you experiencing this for users in just 1 role or is it for users assigned to multiple roles in MNS410? In my experience, I have had to follow a specific process in order to get the desired combination of access for the user in SES401. If this isn't relevant and you are just dealing with users assigned to 1 role, I concur with Karen - removing the user from the role and re-adding should resolve any misconfigurations in SES401.
Regards,
Share a Message
Share a Message
Sometime just changing the validity date in MNS410 does trigger the update of SES401.
MPA
Share a Message
Share a Message