# Upcoming changes to identity management integrations

**URL:** https://forums.rocket.chat/t/upcoming-changes-to-identity-management-integrations/11994
**Category:** Announcements
**Created:** [August 26, 2021, 5:50pm UTC](https://forums.rocket.chat/t/upcoming-changes-to-identity-management-integrations/11994 "2021-08-26T17:50:05Z")
**Posts on this page:** 1
**Showing post:** 65

<div class="post-metadata">

### Author: ![rodrigo.nascimento](https://sea1.discourse-cdn.com/flex021/user_avatar/forums.rocket.chat/rodrigo.nascimento/32/2109_2.png) [@rodrigo.nascimento](https://forums.rocket.chat/u/rodrigo.nascimento)
#### Post date: [September 9, 2021, 7:46pm UTC](https://forums.rocket.chat/t/upcoming-changes-to-identity-management-integrations/11994/65 "2021-09-09T19:46:20Z")

</div>

> [@monkey.bizness](#):
>
> However, I have read this chart and the obvious conclusion is that custom oauth providers are not supported while the built-in ones are.  
> Probably a more accurate description is required.

Thanks for the feedback, we are working to improve those docs pages to be more clear.

> [@monkey.bizness](#):
>
> Second point, “Custom OAuth Role Mapping” support is removed but the description talks about role mapping base on user group. This means that role mapping base on the role claim still works?  
> Again, this is very confusing.

There is only one role setting on Custom OAuth that is the role based on role claim. It will be an enterprise feature.

> [@monkey.bizness](#):
>
> I completely understand the need to make money out of the product. But these method is a bit rough. Having specific feature for the paying customers is a good method. Providing support is another one. Changing the feature set to try to force migrating to a paying plan is also a solution.  
> You have the right to do it. It’s risky and not popular.

Thanks for your comprehension. We understand the risks and how unpopular this changes will be. Unfortunately, support plans or donations only don’t work, we tried as our very first business model 5 years ago. Please join our [Open Call for Community](https://forums.rocket.chat/t/open-call-to-community-re-upcoming-changes-to-identity-management-integrations/12101) tomorrow to know more about this topic.

> [@monkey.bizness](#):
>
> Finally, I am pretty sure to have read in the communication that new features will come to the CE first and then be moved to EE. This means that we can expect the same events for future features.  
> If it’s the case, don’t bother. Noone will use features that will be removed. Instead add them in the edition they belong to from the start and keep them there.  
> Can we have a clarification that?

No, that’s not true, please share with us if you find where this was posted.  
The inverse path may happen, where we deliver features first to EE and make them CE later once we have other features to support the sales. The movement we are doing here is an exception that we don’t want to do again in the future, it’s the first time we are moving a CE feature to EE during these 6 years of our existence and those features were already present in the product before we had our very first EE version, so those never had the possibility to be EE features before the implementation.

---

_[View the full topic](https://forums.rocket.chat/t/upcoming-changes-to-identity-management-integrations/11994)._