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

Implementation of OGC Web Service Security standard #38

Open
cehbrecht opened this issue Apr 12, 2018 · 1 comment
Open

Implementation of OGC Web Service Security standard #38

cehbrecht opened this issue Apr 12, 2018 · 1 comment

Comments

@cehbrecht
Copy link
Member

http://www.opengeospatial.org/pressroom/pressreleases/2746?utm_source=phplist570&utm_medium=email&utm_content=HTML&utm_campaign=OGC+seeks+public+comment+on+Web+Services+Security+Candidate+Standard

@tomLandry
Copy link

We're getting our things together and we'll try to coordinate with our prescribed or proposed approach. It's now quite a long list of things by the way, so that's very good news. Anything following OGC standards will be much more easier to fit in our backlog, that's for sure. Thanks a million times for everything, Carsten and DKRZ.

fmigneault pushed a commit to Ouranosinc/twitcher that referenced this issue Dec 3, 2018
…uth_token to fixes-rebased-on-end2end

* commit 'da3327539fa96580291a1371cb861dd22d38f88f':
  change opensearch query logic to handle multiple eoimage types
  Fix result url in status
  Fix exception handling
  Fix option logic
  Add a config to avoid using auth token to deploy and set visibility
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants