2 Replies Latest reply on Jul 25, 2013 1:51 AM by Scott Wesley

    ORA-20001: Security Group ID (your workspace identity) is invalid

    Scott Wesley

      Hi,

       

      I'm exploring with the concept of creating a user in a predefined workspace, from an APEX application (in development, in a different workspace)

       

      I get the following when executing the following on submit of a page in a "SAGE" workspace

       

      (within package compiled in SYS)

      -- id for workspace 'WS' - predefined, empty workspace

      apex_util.set_security_group_id(123001);

       

      ORA-20001: Security Group ID (your workspace identity) is invalid

      Might this be because I'm attempting this within the context of an APEX session? Am I walking into a dead end?

       

      Cheers

        • 1. Re: ORA-20001: Security Group ID (your workspace identity) is invalid
          flavioc

          Hi Scott,

          I guess you created the package with invoker rights.

          That's the catch or a security protection in other words ;-)

           

          If you create the procedure with standard definer rights, you can switch between different SGIDs (assuming there are multiple workspaces associated to the same oracle schema), but you get the error you've just experienced when this is attempted from a procedure running with invoker rights.

           

          Or, at least, this is my current understanding of the "problem" that, funnily enough, I encountered yesterday.

           

          Flavio

          -----

          http://oraclequirks.blogspot.com

          http://www.yocoya.com

          1 person found this helpful
          • 2. Re: ORA-20001: Security Group ID (your workspace identity) is invalid
            Scott Wesley

            Well thank you for taking the time to share, Flavio.

             

            I just had a look and my package is defined with

            AUTHID CURRENT_USER

            So no doubt in my checkered past usage of this package, I decided it needed to be so.

             

            I'll look into it and see how things may have changed between versions, or maybe changed as I've been imagining things - in my particular scenario.

            It may also be because when I first defined it, I was in a hurry just to find a method of scripting that worked and was efficient on a local environment. Never got a good chance to refine things.

             

            Thanks!