mclark-ably

Sure, heres the code ```python import os import asyncio import aiormq import ssl import logging logging.basicConfig(level=logging.DEBUG) ably_queue_name = os.environ['ABLY_QUEUE_NAME'] ably_host_endpoint = os.environ['ABLY_HOST_ENDPOINT'] ably_host_port = 5671 ably_api_key = os.environ["ABLY_API_KEY"] ably_queue_endpoint =...

A basic message would look like this `id: '0peB9toeCW:0:0', connectionId: '0peB9toeCW', timestamp: 1695029470478, data: 'hello', name: ''`

Thanks @ttypic it was just confusing to see that the SDK logged that it was using token auth e.g. `I/System.out(18365): (INFO): Auth(): using token auth with supplied token only` when...

Hi @lawrence-forooghian 1. This was raised by a customer and after doing a bit of testing I was able to replicate the same. They are using auth_callback now to work...

This [line](https://github.com/ably/ably-python/blob/658b5e904d62a0823e4a007780bb60a10752ff4c/ably/rest/auth.py#L178) in request_token gets the auth_headers and uses those [headers](https://github.com/ably/ably-python/blob/658b5e904d62a0823e4a007780bb60a10752ff4c/ably/rest/auth.py#L220) in the post to the ably requestToken endpoint which I think is where the issue lies as the authorization...

You can try the same from the following code: ``` from flask import Flask,jsonify, make_response, request import json from ably import AblyRest from flask_cors import CORS app = Flask(__name__) CORS(app)...