-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OAUTHBEARER compatibility with GCN #203
Comments
This is supposed to work out of the box, and it seems to for me. Setting up my credential and subscribing from the shell:
Equivalents as python scripts:
Do one or more of these methods not work for you, and if so, what output do you get from |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
I have some collaborators who tried to use a hop consumer client to consume messages from the new GCN kafka servers. In theory this should work because both hop-client and gcn_kafka clients are based on confluent_kafka. However, my collaborators were unable to establish a connection using the standard stream example:
After doing some digging, it looks like the Stream class doesn't allow users to setup the correct OAUTHBEARER authorization method with the client_id and client_secret needed to connect to the GCN servers. This should be possible because I am able to create a hop Consumer as long as I manually pass the appropriate configuration settings:
I used the
igwn.gwalert
topic name here because it's also available form SCIMMA servers. It can be used to check both systems. My collaborators are readingigwn.gwalerts
from SCIMMA servers and need to compare them to notices sent through the GCN servers. They would like to use hop clients for both types of notices to streamline their code.Definition of Done
Have a more straightforward method for connecting to GCN servers using a stream instance. Should not need to pop username and password fields to suppress warnings in the authorization config. Should have a high level method that can easily setup the full GCN server config without needing to manually enter everything.
Tasks/Items:
The text was updated successfully, but these errors were encountered: