glassfish
  1. glassfish
  2. GLASSFISH-14375

create security-realm cannot handle config as target

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 3.1
    • Fix Version/s: 3.1_dev
    • Component/s: security
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

      Description

      This is reported by FishCat member Richard Kolb.
      I can reproduce the problem. Even if specified "default-config" as target, the realm will be created
      to "server-config". After checking with Security and Tom, I was told to file a bug. Here it is.

      To reproduce:

      %asadmin create-auth-realm --classname com.sun.enterprise.security.auth.realm.file.FileRealm –
      target default-config --property file=/tmp/keyfile:jaas-context=fileRealm MyRealm
      Did not find any suitable instances for target default-config; command executed on DAS only

      Command create-auth-realm executed successfully.

      %asadmin list-auth-realms server-config
      admin-realm
      file
      certificate
      MyRealm

      Command list-auth-realms executed successfully.

      list-auth-realms also ignored "default-config" and report whats in "server-config".

      %asadmin list-auth-realms default-config
      Did not find any suitable instances for target default-config; command executed on DAS only
      admin-realm
      file
      certificate
      MyRealm

      Command list-auth-realms executed successfully.

        Activity

        Hide
        kumarjayanti added a comment -

        fixed

        Show
        kumarjayanti added a comment - fixed

          People

          • Assignee:
            kumarjayanti
            Reporter:
            Anissa Lam
          • Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: