If an authorized player disconnects from the server and after that the server is restarted, then the next time the player joins the server, the AuthMeBungee does not recognize that the player is already authorized, although AuthMeReloaded displays a message on the server that the player is authorized.

Terms used below:
bungee-server - BungeeCord-1598 with AuthMeBungee-2.2.0-beta1
authme-server - spigot-1.17.1-3221 with AuthMe-5.6.0-beta2 (AuthMeReloaded)

Short configuration (important parts from config.yml):
bungee-server -> AuthMeBungee:

chatRequiresAuth: true
serverSwitch\requiresAuth: true

authme-server -> AuthMeReloaded:

settings\sessions\enabled: true
Hooks\multiverse: false
Hooks\bungeecord: true

Test case:

1. START bungee-server => OK
2. START authme-server => OK
3. player joins bungee-server -> authme-server => OK
4. chat+server switch+commands does not work (except allowed commands like /login etc.). Works as intented, because the player is not logged-in yet. => OK
5. /login => OK
6. player is disconnected => OK
7. STOP and START authme-server => OK
8. player joins bungee-server -> authme-server => OK
9. Message "Logged-in due to Session Reconnection.". (player is already logged in). Works as intented. => OK
10. ERROR: chat+server switch+commands are still not working. No reaction, no messages. AuthMeBungee blocks them all (except allowed commands like /login etc). Expected: All have to work.
11. player is disconnected => OK
12. player joins bungee-server -> authme-server => OK
13. Message "Logged-in due to Session Reconnection.". (player is already logged in). Works as intented. => OK
14. NOW: chat+server switch+commands work perfectly! AuthMeBungee no longer blocks them. => OK