sso

The upstream issues got closed. It is referenced in:

• client/manager_test_helpers.go#L235

This issue was created by the ORY Closed Reference Notifier GitHub action.

What are you trying to do?

When using the tailscale CLI, it would be very helpful to have shell tab completion for things like subcommands, nodes, and more to make it easier to use.

How should we solve this?

The command line argument parsing library that the CLI currently uses does not support the automatic generation of completion definitions:

Features like tab completion

Expected Behavior

rewriteTarget should work identical for websocket connections and none websocket connections

Current Behavior

For websocket connections, oauth2proxy does not seem to rewrite the request path before sending it to the upstream server.

Example:

...
server:
  BindAddress: 0.0.0.0:8081
  SecureBindAddress: ""
  TLS: null
upstreamConfig:
  upstreams:

Is your feature request related to a problem? Please describe.

The public key-based request signing functionality added to sso_proxy in buzzfeed/sso#106 is undocumented. In particular, it's not immediately obvious how to a) generate an appropriate keypair or b) validate a signed request in an upstream service.

Describe the solution you'd like

New documenta

This will allow users to set up API mgmt for provisioners, and unblock users in environments where the ca.json is not easily accessible.

The --enable-admin flag would create the first provisioner and admin (this code already exists, just behind a boolean).
The --acme flag would create an ACME provisioner.

Related: smallstep/certificates#737

Description

The user should be able to add autocompletion through a cli call (e.g. zitadel completion bash)

Acceptance criteria

• it is possible to add the autocompletion of ZITADEL to .bashrc
• if a user writes zitadel in his terminal and presses tab the user gets proposals of what to do

Describe the issue:
The links not show hover states on hover on the getting started page.

How to reproduce:

1. Navigate to getting started page
2. hover over any link

Expected behavior:
Should indicate hover state for links

Describe the bug

The test case for searching user by custom attributes is wrong here. By the documentation of keycloak rest api, the search params should be like `users.find({ q: 'key1:va