5 Replies Latest reply on Jan 30, 2006 12:53 PM by pmn92

    Portal Instance Authentication

    psalvadori

      Hi all,
      I've a question:
      Is possible to have a different authentication DB for every instance of my portal?
      So, if I enter in one of these instances I need some credentials to access protected area but these credentials are no valid to access protected areas owning to other instances.
      Thanks, Paolo.

      My configuration:
      JBoss-4.0.3SP1
      JBossPortal2.2

        • 1. Re: Portal Instance Authentication

          Define a role and assign users to this role in order to access a portal, page or instance.

          Below I used Authenticated, but any defined role should be fine.

          <security-constraint>
           <policy-permission>
           <role-name>Authenticated</role-name>
           <action-name>view</action-name>
           </policy-permission>
           </security-constraint>
          


          • 2. Re: Portal Instance Authentication
            psalvadori

            Thanks PMO but I'm sorry, I didn't understand what you meant.
            Can explain me deeply how can I define a new role and what xml file I must modify to do what you said? Can You make some example?

            Thanks in advance, Paolo.

            • 3. Re: Portal Instance Authentication
              mjohnpeter

              hi all


              if you don't mind , give me some stuff for programming with portlet in jboss portal

              regards
              Peter

              • 4. Re: Portal Instance Authentication

                The security constraint should be located in the *-object.xml file and can be attached to , or in a deployment.

                Every authenticated user gets the role Authenticated but you can specify any existing role to limit access of a portal, a page or a window to users who have that role (window I did not try).

                • 5. Re: Portal Instance Authentication

                  The security constraint should be located in the *-object.xml file and can be attached to

                  <portal>, <page> or <window>
                  in a deployment.

                  Every authenticated user gets the role Authenticated but you can specify any existing role to limit access of a portal, a page or a window to users who have that role (window I did not try).