Skip to content

Commit ff0b015

Browse files
A follow-up to #2212
References rabbitmq/rabbitmq-server#13541.
1 parent 05a24de commit ff0b015

File tree

3 files changed

+21
-9
lines changed

3 files changed

+21
-9
lines changed

docs/troubleshooting-oauth2.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -37,10 +37,14 @@ a node that is configured to use JWT tokens for authentication and authorization
3737
#### Troubleshooting
3838

3939
Depending on the encoded content, JWT tokens can vary greatly in length.
40-
Messaging protocols supported by RabbitMQ have practical limits on the length of
41-
the password (secret) field.
40+
Messaging protocols supported by RabbitMQ have practical limits on the maximum
41+
frame length.
4242

43-
If a longer token is provided by a client, the connection will be refused with
43+
The default is usually much higher than a practically possible JWT token length,
44+
for example, for AMQP 0-9-1 and the [RabbitMQ Stream Protocol](./stream) the default
45+
is 128 kB. However, the maximum frame limit can be overriden [via `rabbitmq.conf`](./configure) and via client library configuration.
46+
47+
If a long token is provided by a client and a lower limit is configured, the connection will be refused with
4448
a "frame length exceeded", "frame is too large" and similar error messages
4549
in [server logs](./logging).
4650

versioned_docs/version-3.13/troubleshooting-oauth2.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -37,10 +37,14 @@ a node that is configured to use JWT tokens for authentication and authorization
3737
#### Troubleshooting
3838

3939
Depending on the encoded content, JWT tokens can vary greatly in length.
40-
Messaging protocols supported by RabbitMQ have practical limits on the length of
41-
the password (secret) field.
40+
Messaging protocols supported by RabbitMQ have practical limits on the maximum
41+
frame length.
4242

43-
If a longer token is provided by a client, the connection will be refused with
43+
The default is usually much higher than a practically possible JWT token length,
44+
for example, for AMQP 0-9-1 and the [RabbitMQ Stream Protocol](./stream) the default
45+
is 128 kB. However, the maximum frame limit can be overriden [via `rabbitmq.conf`](./configure) and via client library configuration.
46+
47+
If a long token is provided by a client and a lower limit is configured, the connection will be refused with
4448
a "frame length exceeded", "frame is too large" and similar error messages
4549
in [server logs](./logging).
4650

versioned_docs/version-4.0/troubleshooting-oauth2.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -37,10 +37,14 @@ a node that is configured to use JWT tokens for authentication and authorization
3737
#### Troubleshooting
3838

3939
Depending on the encoded content, JWT tokens can vary greatly in length.
40-
Messaging protocols supported by RabbitMQ have practical limits on the length of
41-
the password (secret) field.
40+
Messaging protocols supported by RabbitMQ have practical limits on the maximum
41+
frame length.
4242

43-
If a longer token is provided by a client, the connection will be refused with
43+
The default is usually much higher than a practically possible JWT token length,
44+
for example, for AMQP 0-9-1 and the [RabbitMQ Stream Protocol](./stream) the default
45+
is 128 kB. However, the maximum frame limit can be overriden [via `rabbitmq.conf`](./configure) and via client library configuration.
46+
47+
If a long token is provided by a client and a lower limit is configured, the connection will be refused with
4448
a "frame length exceeded", "frame is too large" and similar error messages
4549
in [server logs](./logging).
4650

0 commit comments

Comments
 (0)