Okta - import user & group - default behaviour
0 vote
Dear support,
The default behaviour, when we are in user "import user from Okta", start to browse every user from Okta database.
I'm a very large compagny with more than 50k user, and the request is very low & buggued.
There is a growth of RAM in each internet browser, and finally when it didn't fail i can select / filter user.
Same problem, when i try to use the filter "group", it start to request/list all Active Directory group from okta, which goes very slow, very high consumption of RAM, (more than 2Go), and never success to list.
Would it be possible to change the default behaviour ? by not request okta, and wait for "specific request" in search field by user ?
Regards,
Damien
All Comments (8)
Hello Damien,
Thank you for your request. I'm creating a ticket to investigate how it could be improved. The best way to fix that would be to have a better API from Okta to browse users; we will check if they have improved it lately. Otherwise, as you mentioned, we could avoid loading all users and instead enforce a filter. We will look into that as soon as possible. I can't provide an ETA, but we will post back here once we have an update. Meanwhile, you should be able to add your users manually if you know exactly the username or the group name (if you have a similar issue with groups).
Best regards,
François Dubois
Hello,
Thank for your reply !
Exactly I can import user with, "create new user", then select "okta", and then type user.name@company.com, it will look in okta database to see if user exist.
It seems that with devolution server last update it get worst.
Regards,
Damien
Hello Damien,
It seems that with devolution server last update it get worst.
I'm sorry to hear that. Did you get any other issue with Devolutions Server ? What version do you use ? Don't hesitate to write us with your different issues, we will help with pleasure.
Best regards,
François Dubois
Hello,
We use devolution server 2024.3.10.0.
I didn't detect any other issue for now.
Regards,
Damien
Hello,
I did some test :
- With DVLS server : 2024.2.13.0 -> Okta request is slow, but :
- i can list all okta user and import some of them
- i can list all user groupe and select on to filter user within this group.
- With DVLS server : 2024.3.10.0 -> Okta request is very very very slow
- i can list all okta user and import some of them
- i can't list user groupe , browser failed list them with high RAM consumption.
Regards,
Damien
Hello Damien,
Thank you for bringing this issue to our attention. I don't see any good reason why it would be slower. We are investigating and will give you news as soon as possible.
Best regards,
François Dubois
Hi Damien,
We need to make some changes to how we internally handle paging to better utilize Okta's API. The changes will be coming in a later release of Devolutions Server.
Best regards,
Alexandre Martigny
Hi Damien,
We need to make some changes to how we internally handle paging to better utilize Okta's API. The changes will be coming in a later release of Devolutions Server.
Best regards,
Thank you for your feed back.
Hope you will soon find a solution to this issue.
Regards,
Damien