fedora-infrastructure

#7710 [fedora-messaging] Generate keypair for retrace.fedoraproject.org
Closed: Fixed by kevin. Opened by mkutlak.

Closed: Fixed
Reopen Issue

We (retrace.fedoraproject.org) seem to be missing a necessary certificate/key to connect to the rabbitmq /pubsub to publish fedora-messaging messages to faf queue.

Can someone create a pair for us?

So we can add them [tls] section in /etc/fedora-messaging/config.toml.

So, to be clear:

  • You need/want only production certs, not staging

  • The service is actually 'faf' so, we should name the cert 'faf' (In fedmsg we named certs for sending machine, but with fedora-messaging we are doing a cert per service)

Metadata Update from @kevin:
- Issue assigned to kevin
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: authentication

@mkutlak Any news here?

You need/want only production certs, not staging

Yes, production certs only.

The service is actually 'faf' so, we should name the cert 'faf' (In fedmsg we named certs for sending machine, but with fedora-messaging we are doing a cert per service)

Yes, the service should be called 'faf'.

@mkutlak Any news here?

Is there anything that I should do?

Done. The cert can be referred from ansible with:

"{{private}}/files/rabbitmq/{{env}}/pki/issued/faf.crt"
"{{private}}/files/rabbitmq/{{env}}/pki/private/faf.key"
"{{private}}/files/rabbitmq/{{env}}/pki/ca.crt"

Let us know if you need anything else.

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

Thank you.

Metadata

authentication

None
None
Normal
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.