Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-2230

Realm name not taken into account for RBAC role mapping using legacy security realm.

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • 3.0.0.Alpha23
    • 3.0.0.Alpha22
    • Security
    • None
    • Hide
      1. start WildFly
      2. /core-service=management/access=authorization/role-mapping=Administrator:add()
      3. /core-service=management/access=authorization/role-mapping=Administrator/include=aministrator:add(name=administrator, type=user, realm=ManagementRealm)
      4. enable RBAC: /core-service=management/access=authorization:write-attribute(name=provider, value=rbac)
      5. add user: ./add-user.sh -u 'administrator' -p 'password1!'
      6. reload
      7. open web console and login user
      Show
      start WildFly /core-service=management/access=authorization/role-mapping=Administrator:add() /core-service=management/access=authorization/role-mapping=Administrator/include=aministrator:add(name=administrator, type=user, realm=ManagementRealm) enable RBAC: /core-service=management/access=authorization:write-attribute(name=provider, value=rbac) add user: ./add-user.sh -u 'administrator' -p 'password1!' reload open web console and login user

    Description

      Console is not able to connect to management interface.

      Attachments

        Issue Links

          Activity

            People

              darran.lofthouse@redhat.com Darran Lofthouse
              darran.lofthouse@redhat.com Darran Lofthouse
              Pavel Jelinek Pavel Jelinek
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: