Hi,

Unfortunately this version of the spec didn't managed to implement the authorization part and basically only deals with authentication.

However the Servlet spec has since the beginning the security-constraint element in the web.xml deployment descriptor. This is the only standard way to restrict role access to pages.

You have some good information on the Java EE 7 tutorial: https://docs.oracle.com/javaee/7/tutorial/security-webtier002.htm

Where restricing based on roles, note that there are two special built-in ones, "*" and "**": 

- * means any authenticated user which has at least one role, whatever it is, is granted access.

-  ** means any autenticated user, even users without roles.

Regards,

Guillermo González de Agüero

El mié., 9 de agosto de 2017 21:51, Saeed <sinaisix@...> escribió:

Hi. I've been looking at the test examples and so far I'm able to follow them. However I'm at a loss about how to declare a specific set of say JSF pages as protected.

In Shiro, I can declare in the shiro.ini file that /foo/* is protected so only logged in users with certain roles can access it.

I'm not sure if I've seen such with JSec yet.  Again pardon me if I miss the obvious.

Thanks in advance

 

On 9 Aug 2017 17:46, "Guillermo González de Agüero" <z06.guillermo@...> wrote:

Great to hear that! The tests are indeed the best way to get started right now.

We an to write some documentation but we're still busy finishing Soteria for its release in the next couple of weeks.

Please don't hesitate to ask for help on any doubt you have. And we will specially welcome any bug reports you can make.

Hope you enjoy!

Regards,

Guillermo González de Agüero

El mié., 9 de agosto de 2017 15:07, Saeed <sinaisix@...> escribió:

Thanks. Got it to work. Checking out the samples in the RI code repo. I think I'm getting the hang of this, coming from the Apache Shiro way of thinking. Once again thanks everyone for your input

Luqman 

+233-504-733076

On 8 August 2017 at 17:48, Guillermo González de Agüero <z06.guillermo@...> wrote:

Hi Saaed,

Thanks for your interest! As Will has already stated, latest promoted versions of GlassFish already integrate JSR 375, so you won't need Soteria dependency, just the API.

The latest version GlassFish has integrated is 1.0-b11 [1] so your dependency should be:

<dependency>
    <groupId>javax.security.enterprise</groupId>
    <artifactId>javax.security.enterprise-api</artifactId>
    <version>1.0-b11</version>
    <scope>provided</scope>
</dependency>

The problem you are finding is that artifacts are still not being uploaded to Maven Central, but to java.net, so you will need to add the Java.net Maven repository:

<repository>
    <id>java-net</id>
    <name>Java.net</name>
    <url>https://maven.java.net/content/repositories/releases/</url>
</repository>

GlassFish has just upgraded the version, so you should better try a nightly build if possible to benefit of the latest bugfixes.

Pleas don't forget to create issues for any bug or inconsistency you find!

Regards,

Guillermo González de Agüero

[1] https://github.com/javaee/glassfish/pull/22190/files

El mar., 8 ago. 2017 a las 19:33, Saeed (<sinaisix@...>) escribió:

Hello everyone from Accra Ghana. I would like to test out Soteria with the just published Glassfish promoted build 18. However adding the following dependency to my pom.xml results in maven throwing an error saying it cannot locate the artifacts. Pardon my ignorance if the solution is something very simple. Thanks in advance. 

 <dependency>
            <groupId>javax.security</groupId>
            <artifactId>javax.security-api</artifactId>
            <version>1.0-m01</version>
        </dependency>
        <dependency>
            <groupId>org.glassfish.soteria</groupId>
            <artifactId>soteria</artifactId>
            <version>1.0-m01</version>
        </dependency>