Is it possible to restrict content editing in classic mode ? | Community
Skip to main content
nagasreenug4839
nagasreenug4839
Level 2
October 4, 2018
Solved

Is it possible to restrict content editing in classic mode ?

  • October 4, 2018
  • 4 replies
  • 1737 views

Hi All,

Recently we got requirement from client, client want to restrict content authoring in classic mode (cf#) based on usergroup .Is it possible to restrict like that ?

Client want users need to authoring content in touch ui mode not in classic mode.,Even if users forcibly open page in classic mode(page open with  CF#) we should not allow the access.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by raj_mandalapu

You need to use sling filters and need to follow below design.

Steps :

  • As you are using author instance so you must execute only in author environment. you must add this in run mode configurations
  • Inside doFilter() method you need to check the URL contains "cf#" or not. and it is good to check run mode also author or publish along with "cf#"
  • Use configuration manager to configure groups
  • Read groups from the configurations and iterate
  • Now get the username and check whether he is in a particular group or not
  • If the user in a specified group then you can perform redirection to touch UI page, by replacing "cf#" to "editor.html"

Example :

http://keysandstrokes.info/aem-sling-filters/

4 replies

arunpatidar
Community Advisor
arunpatidarCommunity Advisor
Community Advisor
October 4, 2018

Hi,

You can do this with the help of filters.

As soon as user arrives in classic UI, it will be redirected to Touch UI.

E.g. Redirect user to classic UI welcome screen based on userid/group

https://github.com/arunpatidar02/aem63app-repo/blob/master/java/CustomScreenFilter.java

You can do similar.

Arun Patidar
raj_mandalapu
raj_mandalapuAccepted solution
Level 7
October 4, 2018

You need to use sling filters and need to follow below design.

Steps :

  • As you are using author instance so you must execute only in author environment. you must add this in run mode configurations
  • Inside doFilter() method you need to check the URL contains "cf#" or not. and it is good to check run mode also author or publish along with "cf#"
  • Use configuration manager to configure groups
  • Read groups from the configurations and iterate
  • Now get the username and check whether he is in a particular group or not
  • If the user in a specified group then you can perform redirection to touch UI page, by replacing "cf#" to "editor.html"

Example :

http://keysandstrokes.info/aem-sling-filters/

    smacdonald2008
    smacdonald2008
    Level 10
    October 4, 2018

    great responses!

    nagasreenug4839
    nagasreenug4839Author
    Level 2
    October 5, 2018

    Thank you Rajas, I will try with your suggested approach and update you.

    Terms & ConditionsAccessibility statement

    Loading footer...