We have recently been told that as part of the move to the new Request Center in January 2024, ALL access profiles in our tenant will have their Requestable attribute set to true, even if they are currently set to requestable = false.
Since we have some Access Profiles that must not be requestable, we have been told that we will need to go back into IDN post migration to the new Request Center and reset the value of the requestable attribute to false on those access profiles.
The unusualness of this “hey we’re going to change your existing data when we roll out this new UX element” strangeness aside, I need to build out a process where I can:
Pre-Migration, capture a list of access profiles have requestable = false
Post Migration, submit an API call that for those access profiles that were set to false, to set them again to false.
I believe that I need the capture Api call to output a list of access profile IDs.
I believe I then need to submit those IDs via an API that changes their requestable to false.
I am not familiar with APIs that can work this way and considering we have many access profiles that must not be requestable, we are trying to understand how we can quickly get back to our pre-request center migration quickly,
This is a list of all the Access Profiles in your Tenant.
Right click Access Profiles and select “Export all Access profiles as CSV…”
take note of where the file is being saved.
Open the file and you will have a list of all your Access Profiles! Success!
You should be able to filter on “Requestable” in the excel document to find the one’s that are false. (At least this way you can keep track of them.)
Another way to preserve all of this is to use the Configuration Hub.
The Configuration Hub will allow you to create a Backup of all your Sources or whatever. Once you have that backup, you can effectively delete your Sources and restore them with the backup! (The username and passwords might need to be re-entered though.)
Follow the instructions on the Configuration Hub page to backup and restore your Tenant Config. Then you won’t have to worry about doing any of that manual labor of tracking your Access Profiles.
I have not yet used the Configuration hub before, so keep forgetting about it.
Its a great idea… I think we are going to be migrated to the new request center on January 22nd, so if we take an access profile backup on the 21st, and apply it right after the migration, we have an easy way to get our access profiles back to their non requestable state!
Exactly! And if you want to test it to make sure it all works, try the back up process in Configuration Hub now. Make a noticeable change to one of your sources. Like mark an Access Profile as not Requestable, or mark ALL your entitlements on a Source as Requestable, then restore everything from your backup.
It’s like magic!
Don’t forget to mark answers as Solutions if it works out for you and let me know if you have any other questions!
