OGC API Records / Use GN5 app#149
Open
fxprunayre wants to merge 2 commits into
Open
Conversation
Configuring OGC API Records service to use GN5 more robust and complete implementation instead of the microservices module.
This reverts commit 1a9dfc1.
tanzeeladebont
force-pushed
the
feature/ogcapirecord-on-gn5
branch
from
791deaf to
8fffe4b
Compare
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Configuring OGC API Records service to use GN5 more robust and complete implementation instead of the microservices module.
After start, can be tested by browsing
The OGC API service only serves public records (like previous microservice implementation). The
MicroServicesProxydo not forward auth/session. To support access of private records, the other setup is to put GN5 on top handling authentication.