Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extracted mappings still contain regex matching expressions #1413

Closed
odrotbohm opened this issue Dec 12, 2020 · 0 comments
Closed

Extracted mappings still contain regex matching expressions #1413

odrotbohm opened this issue Dec 12, 2020 · 0 comments
Assignees
Labels
in: core Core parts of the project type: bug
Milestone

Comments

@odrotbohm
Copy link
Member

Baclport of ##1412.

@odrotbohm odrotbohm added type: bug in: core Core parts of the project labels Dec 12, 2020
@odrotbohm odrotbohm added this to the 1.2.3 milestone Dec 12, 2020
@odrotbohm odrotbohm self-assigned this Dec 12, 2020
odrotbohm added a commit that referenced this issue Dec 12, 2020
We now remove potentially used regular expression matchers from template variables to avoid the to show up in links generated for the templates.

Backport of #1412.
odrotbohm added a commit to quarano/quarano-application that referenced this issue Dec 14, 2020
We now require authentication to the role of THIRD_PARTY for all requests to URIs starting with /ext. This currently contains the API to submit visitor groups for occasions.

To test this, the repository now contains a sample client and server key, key store and trust store infrastructure. The key- and trust stores are also bundled with the artifact if the localDev Maven profile is activated during the build. This allows the certificate authentication to also be used during local executions.

The API root resource now exposes some links that are dependent on the current user's role:

* login, reset-password - if the resource is accessed without authentication at all or any role that's assignable to humans.
* submit-visitors - if the resource is accessed by third-party software

Temporarily introduced a patched copy of Spring HATEOAS' AnnotationMappingDiscoverer to benefit from the fix for [0] until we can upgrade to a released version of it.

Additional security reference documentation for developers, deployments and third-party integrators.

[0] spring-projects/spring-hateoas#1413
elseppo pushed a commit to quarano/quarano-application that referenced this issue Dec 27, 2020
We now require authentication to the role of THIRD_PARTY for all requests to URIs starting with /ext. This currently contains the API to submit visitor groups for occasions.

To test this, the repository now contains a sample client and server key, key store and trust store infrastructure. The key- and trust stores are also bundled with the artifact if the localDev Maven profile is activated during the build. This allows the certificate authentication to also be used during local executions.

The API root resource now exposes some links that are dependent on the current user's role:

* login, reset-password - if the resource is accessed without authentication at all or any role that's assignable to humans.
* submit-visitors - if the resource is accessed by third-party software

Temporarily introduced a patched copy of Spring HATEOAS' AnnotationMappingDiscoverer to benefit from the fix for [0] until we can upgrade to a released version of it.

Additional security reference documentation for developers, deployments and third-party integrators.

[0] spring-projects/spring-hateoas#1413
odrotbohm added a commit that referenced this issue Feb 10, 2021
…ressions.

Switched to manual parsing of template variables as regular expressions can contain { and } characters which makes matching variables using these as delimiters impossible.

Related ticket: #1413.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: core Core parts of the project type: bug
Projects
None yet
Development

No branches or pull requests

1 participant