Permissions issue after upgrade to 8.0.2

Did you check if the permissions are gone (with Designer) or are you experiencing issues? If you see some permissions issues it might be due to the fix for 30052 as mentioned in the release notes.

If you had explicit insert permissions on a table (not edit) but on the columns you had only edit permissions in combination with permissions originating from different permissions groups you might experience some issues. You might need to add the additional insert permissions on the columns.

In addition, you might want to check the setting of the config parm Common\AutoExtendPermissions.

Did you check if the permissions are gone (with Designer) or are you experiencing issues? If you see some permissions issues it might be due to the fix for 30052 as mentioned in the release notes.

If you had explicit insert permissions on a table (not edit) but on the columns you had only edit permissions in combination with permissions originating from different permissions groups you might experience some issues. You might need to add the additional insert permissions on the columns.

In addition, you might want to check the setting of the config parm Common\AutoExtendPermissions.

After looking further we realized it may not be issue with permissions not copying over. We assigned CCC_4_ALLUSER (copy of VI_4_ALLUSER) permission group to all users in our old environment. However, the copy removed this permission group for all users. Is there a way this can be re-assigned to all users again without having to run a SQL query on the DB?

You should be able to go to One Identity Manager Administration within Manager and navigate to Base roles\Everyone (Change), click on the role and then click on change master data. Here you can switch the Permissions group to your CCC_4_ALLUSER

Thanks Troy. It helped. How do we turn off the password changes that came with 8.0.2? Is there a confir param for this?

What do you want to turn off exactly? That the passwords used by the Person authenticators are expiring or that the users are getting informed about the expiry?

We dont manage passwords from 1IM. I have noticed that ( in our DEV environment), if the login option is set as Employee role based, it would log us in with the username and a password was not required (v7.1.2). However with 8.0.2, we have to set a password for an employee in 1IM to login. How can we overcome that?

smmellac said:

username and a password was not required (v7.1.2)

Take a look at the documentation for password policies.  https://support.oneidentity.com/technical-documents/identity-manager/8.0.2/configuration-guide/22#TOPIC-1022948

In addition to the link from George, you will find more about the new security measures in version 8 in the release notes of 8.0 https://support.oneidentity.com/technical-documents/identity-manager/8.0/release-notes/

Thanks Goerge and Markus.