eclipse-ee4j / eclipse-ee4j/exousia

Cannot specify INTEGRAL as transport-guarantee Type

Open
#19 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
14
Forks
8
PR merge metrics
No merged PRs in 30d

Description

Servlet 6.0 schema says that we can specify INTEGRAL as the type of transport-guarantee.

refs) https://jakarta.ee/xml/ns/jakartaee/web-common_6_0.xsd
```xml

The transport-guaranteeType specifies that the communication between client and server should be NONE, INTEGRAL, or CONFIDENTIAL. NONE means that the application does not require any transport guarantees. A value of INTEGRAL means that the application requires that the data sent between the client and server be sent in such a way that it can't be changed in transit. CONFIDENTIAL means that the application requires that the data be transmitted in a fashion that prevents other entities from observing the contents of the transmission. In most cases, the presence of the INTEGRAL or CONFIDENTIAL flag will indicate that the use of SSL is required. Used in: user-data-constraint

```

like
```


integral
/integral


INTEGRAL ★


```

On the other hand, Exousia uses ServletSecurity.TransportGuarantee in SecurityConstraint (instead of jakarta.security.jacc.WebUserDataPermission).
https://github.com/eclipse-ee4j/exousia/blob/ebdd1a2f0bcf70deec6ffdf111c4ff6195f186cd/impl/src/main/java/org/glassfish/exousia/constraints/SecurityConstraint.java#L35
ServletSecurity.TransportGuarantee does not have INTEGRAL as its API, so we cannot use this type.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.