It sounds as if you've worked with Azure AD support, so I may be mistaken in this suggestion, but if not, it might be a quick fix. I believe that Azure AD has a configuration in either the application or the claim that allows you to specify which groups would be included the group claim. Presuming you have fewer than 150 AEM-relevant groups, if that configuration exists, you should be able to have Azure AD in effect filter the group claim to only specific groups that are relevant. I may be think...

Referring to the original implementation of styles plugin/libs/clientlibs/granite/coralui2/optional/rte/js/components/rte/plugins/StylesPlugin.js Configs are taken from styles node in the rtePlugins config in componentOverlay this file, have a separate node structure outside component to maintain css styles the way you do in plugin config.Change method getStyles in above file to read the values from you node structure based on the current page hierarchy

Hi Nisha,ADFS/SAML imleplementation1. Implement SAML Server and provide ADFs as Identity Provider inside that.2. Connect SAML as Auth Handler.When an internal user will try to login he will be redirected to SAML where if user is already logged in using ADFs then he will be authenticated in AEM autmatically.External User issue1. Implment another login page for External user and then authenticate them using AEM USers.2. Keep a flag for all the users if they are internal or external to identify.Don...