b3xeh (b3xeh) asked a question.
Having OKTA provision a Salesforce user is great and saves us time when setting up new users, but we ran into an issue where we wanted to deactivate users, but OKTA seemed to reactivate them since the user was still in a provisioning group. This has caused us to run into licensing issues in Salesforce. Can we let OKTA do everything but check the Salesforce user activation box?
So in this case, the user is active still in Okta but you want the user to be deactivated in Salesforce? With the "Create", "Update", & "Deactivate" boxes checked, Okta will fully control the user account that was provisioned to Salesforce.
In your case, sounds to me like you would want to uncheck the "Update" box. Now, the concern here is that if users undergo profile changes, such as new last names, emails, locations, etc., it would not update in Salesforce. On the other hand, the account would not be reactivated either I do not think.
I do not think the user reactivation is done via the "create" checked box, but honestly you may need to test that as looking at the documentation it appears that it might be responsible for this. If it is, naturally that will complicate things. At the end of the day, your best bet is really to just remove them from the Salesforce assignment in which case they would be deactivated in Salesforce as a result. Hopefully that helps.
Thanks!
We use cookies to provide the best website experience and to help understand marketing efforts. We may also share data with ad partners to reach potential customers across the web. To learn more, visit our Privacy Policy. Click here for Your Privacy Choices. You may also opt out of this sharing by signaling your preference via GPC, applicable only to the browser signaling the opt-out.
More information
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.
These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising.
Select All
We use cookies to provide the best website experience and to help understand marketing efforts. We may also share data with ad partners to reach potential customers across the web. To learn more, visit our Privacy Policy. Click here for Your Privacy Choices. You may also opt out of this sharing by signaling your preference via GPC, applicable only to the browser signaling the opt-out.
More information
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.
These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising.
Select All
So in this case, the user is active still in Okta but you want the user to be deactivated in Salesforce? With the "Create", "Update", & "Deactivate" boxes checked, Okta will fully control the user account that was provisioned to Salesforce.
In your case, sounds to me like you would want to uncheck the "Update" box. Now, the concern here is that if users undergo profile changes, such as new last names, emails, locations, etc., it would not update in Salesforce. On the other hand, the account would not be reactivated either I do not think.
I do not think the user reactivation is done via the "create" checked box, but honestly you may need to test that as looking at the documentation it appears that it might be responsible for this. If it is, naturally that will complicate things. At the end of the day, your best bet is really to just remove them from the Salesforce assignment in which case they would be deactivated in Salesforce as a result. Hopefully that helps.
Thanks!