You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, using version 1.4.3 there is great support for spring-data-rest endpoint documentation.
Do you think it is possible to extend that support to the "@securityrequirement" annotation?
No matter whether it's placed on the interface anntotaed with "@RepositoryRestResource" or any of the methods within - there is just no "security" element on any of the paths.
Is this something you can add, or is the original annotation just not passed on to the dynamic controllers when they are created in spring-data-rest (version of spring-data-rest is 3.2.7.RELEASE as defined by spring-boot-starter-parent 2.2.7.RELEASE)?
It would be great if the behavior of the "@securityrequirement" annotation could be aligned with that of the "@PreAuthorize"/"@secured" annotations on RepositoryRestResources.
The text was updated successfully, but these errors were encountered:
Such a feature is not yet planned.
You can add security requirements to your desired spring-data-rest endpoints using OpenApiCustomiser, and here is a sample code for that:
Hi, using version 1.4.3 there is great support for spring-data-rest endpoint documentation.
Do you think it is possible to extend that support to the "@securityrequirement" annotation?
No matter whether it's placed on the interface anntotaed with "@RepositoryRestResource" or any of the methods within - there is just no "security" element on any of the paths.
Is this something you can add, or is the original annotation just not passed on to the dynamic controllers when they are created in spring-data-rest (version of spring-data-rest is 3.2.7.RELEASE as defined by spring-boot-starter-parent 2.2.7.RELEASE)?
It would be great if the behavior of the "@securityrequirement" annotation could be aligned with that of the "@PreAuthorize"/"@secured" annotations on RepositoryRestResources.
The text was updated successfully, but these errors were encountered: