2 configurations for the listeners are now possible: - enableJWT=false with client ssl auth - enableJWT=true with https Actual verification of the tokens is handled by https://github.com/openshift-online/ocm-sdk-go. An authentication handler is run as the top level handler, before any routing is done. Routes which do not require authentication should be listed as exceptions. Authentication can be restricted using an ACL file which allows filtering based on JWT claims. For more information see the inline comments in ocm-sdk/authentication. As an added quirk the `-v` flag for the osbuild-composer executable was changed to `-verbose` to avoid flag collision with glog which declares the `-v` flag in the package `init()` function. The ocm-sdk depends on glog and pulls it in.
18 lines
884 B
Go
18 lines
884 B
Go
// Package jsoniter implements encoding and decoding of JSON as defined in
|
|
// RFC 4627 and provides interfaces with identical syntax of standard lib encoding/json.
|
|
// Converting from encoding/json to jsoniter is no more than replacing the package with jsoniter
|
|
// and variable type declarations (if any).
|
|
// jsoniter interfaces gives 100% compatibility with code using standard lib.
|
|
//
|
|
// "JSON and Go"
|
|
// (https://golang.org/doc/articles/json_and_go.html)
|
|
// gives a description of how Marshal/Unmarshal operate
|
|
// between arbitrary or predefined json objects and bytes,
|
|
// and it applies to jsoniter.Marshal/Unmarshal as well.
|
|
//
|
|
// Besides, jsoniter.Iterator provides a different set of interfaces
|
|
// iterating given bytes/string/reader
|
|
// and yielding parsed elements one by one.
|
|
// This set of interfaces reads input as required and gives
|
|
// better performance.
|
|
package jsoniter
|