diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 8014a05..189a1ba 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -4,7 +4,7 @@ Thanks for your interest in this project. ## Project description -The Java EE security provides a set of required security functionalities +Jakarta Security provides a set of required security functionalities including authentication, authorization, data integrity, and transport security. * https://projects.eclipse.org/projects/ee4j.es diff --git a/README.md b/README.md index f7b9587..28c966a 100644 --- a/README.md +++ b/README.md @@ -1,13 +1,13 @@ -# JSR-375 API Code Repository +# Jakarta Security -This repository contains the code for the Java EE Security API (JSR-375). +This repository contains the code for Jakarta Security. [Online JavaDoc](https://javadoc.io/doc/javax.security.enterprise/javax.security.enterprise-api/) Building -------- -JSR 375 API can be built by executing the following from the project root: +Jakarta Security can be built by executing the following from the project root: ``mvn clean package`` @@ -18,7 +18,7 @@ Making Changes To make changes, fork this repository, make your changes, and submit a pull request. -About JSR-375 +About Jakarta Security ------------- -For more information about JSR-375, see the project web site at [https://javaee.github.io/security-spec/](https://javaee.github.io/security-spec/). +For more information about Jakarta Security, see the project web site at [github.com/eclipse-ee4j/security-api](https://github.com/eclipse-ee4j/security-api). diff --git a/pom.xml b/pom.xml index 3204b6b..a080c2d 100644 --- a/pom.xml +++ b/pom.xml @@ -31,8 +31,11 @@ 1.0.2-SNAPSHOT bundle - Enterprise Security API - Security API for Java EE Applications + Jakarta Security + + Jakarta Security defines a standard for creating secure Jakarta EE applications in modern application paradigms. + It defines an overarching (end-user targeted) Security API for Jakarta EE Applications. + 2015 @@ -181,7 +184,7 @@ ${spec.implementation.version} ${spec.specification.version} - EE Security API ${spec.version} Specification + Jakarta Security ${spec.version} Specification Oracle Corporation ${project.organization.name} diff --git a/src/main/java/javax/security/enterprise/AuthenticationException.java b/src/main/java/javax/security/enterprise/AuthenticationException.java index 3a45a59..eed0ec5 100644 --- a/src/main/java/javax/security/enterprise/AuthenticationException.java +++ b/src/main/java/javax/security/enterprise/AuthenticationException.java @@ -23,9 +23,10 @@ /** * A generic authentication exception. * - * This exception corresponds to the JASPIC (JSR 196) AuthException in that whenever a method - * from the {@link HttpAuthenticationMechanism} throws this exception, the JASPIC bridge - * has to throw an AuthException back to the JASPIC runtime wrapping this exception. + * This exception corresponds to the Jakarta Authentication AuthException in that whenever a + * method from the {@link HttpAuthenticationMechanism} throws this exception, the Jakarta Authentication + * bridge has to throw an AuthException back to the Jakarta Authentication runtime wrapping + * this exception. * */ public class AuthenticationException extends GeneralSecurityException { diff --git a/src/main/java/javax/security/enterprise/AuthenticationStatus.java b/src/main/java/javax/security/enterprise/AuthenticationStatus.java index 40235a8..003dcae 100644 --- a/src/main/java/javax/security/enterprise/AuthenticationStatus.java +++ b/src/main/java/javax/security/enterprise/AuthenticationStatus.java @@ -26,7 +26,7 @@ * *

* For the result from {@link HttpAuthenticationMechanism#validateRequest(javax.servlet.http.HttpServletRequest, javax.servlet.http.HttpServletResponse, javax.security.enterprise.authentication.mechanism.http.HttpMessageContext)} - * an AuthenticationStatus must be transformed by the Java EE server into the corresponding JASPIC (JSR 196) AuthStatus + * an AuthenticationStatus must be transformed by the Jakarta EE server into the corresponding Jakarta Authentication AuthStatus * according to the following rules: * *

* *

- * After the transformation as outlined above the transformed result has to be processed by the Java EE server as - * specified by the Servlet Container Profile of the JASPIC 1.1 spec (chapter 3). + * After the transformation as outlined above the transformed result has to be processed by the Jakarta EE server as + * specified by the Servlet Container Profile of the Jakarta Authentication spec. * *

- * Implementation note: while the JASPIC Servlet Container Profile is the authoritative + * Implementation note: while the Jakarta Authentication Servlet Container Profile is the authoritative * source on how to process the AuthStatus.SUCCESS result and this specification puts no constraints - * of any kind on that, the expectation is that Java EE servers in practice will mainly look at the + * of any kind on that, the expectation is that Jakarta EE servers in practice will mainly look at the * result being AuthStatus.SUCCESS or not AuthStatus.SUCCESS. Simply said, if the result is * AuthStatus.SUCCESS the authenticated identity (if any) must be set (established) for the current HTTP request, * otherwise not. @@ -51,7 +51,7 @@ *

* The return value of {@link SecurityContext#authenticate(javax.servlet.http.HttpServletRequest, javax.servlet.http.HttpServletResponse, javax.security.enterprise.authentication.mechanism.http.AuthenticationParameters)} * , which is also of type AuthenticationStatus, strongly relates to the outcome of the HttpAuthenticationMechanism#validateRequest - * method as described above, but must be transformed by the Java EE server from the corresponding outcome of the + * method as described above, but must be transformed by the Jakarta EE server from the corresponding outcome of the * {@link HttpServletRequest#authenticate(javax.servlet.http.HttpServletResponse)} call as follows: * *