File: rabbitmq.html

package info (click to toggle)
rabbitmq-server 4.0.5-8
  • links: PTS, VCS
  • area: main
  • in suites: sid
  • size: 37,972 kB
  • sloc: erlang: 257,835; javascript: 22,466; sh: 3,037; makefile: 2,517; python: 1,966; xml: 646; cs: 335; java: 244; ruby: 212; php: 100; perl: 63; awk: 13
file content (23 lines) | stat: -rw-r--r-- 1,087 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
<h1> FakePortal </h1>

<p>This is a portal used to test <b>Identity-Provider-based authentication</b>.
This means users comes to RabbitMQ with a token already obtained without involving RabbitMQ
management ui.
</p>

<p>There are two ways to access RabbitMQ management ui when using `idp-initiated` mode. These are: </p>

<h2>Inject access_token into the HTTP Authorization header as Bearer token</h2>
This mechanism is used by proxies. Before the request is forwarded to the proxied RabbitMQ URL, the
access token is injected into the Authorization header.
</p>
<a href="<%= proxied_url %>">RabbitMQ Management ui</a>

<h2>POST access_token to /login endpoint</h2>
This mechanism is available for those portals which cannot inject the access token into the Authorization <b>header</b>.
Instead they submit the access token via the form field <b>access_token</b> to the RabbitMQ <b>/login</> endpoint.
</p>
<form action="<%= url %>" id="login_form" method="POST">
  <input type="hidden" name="access_token" value="<%= access_token %>">
  <input type="submit" value="<%= name %>">
</form>