Reservation Error in Horde

I have another question, and instead of starting a new thread, I’ll ask it here:

What is the intended pipeline for build agents to authenticate in Horde? I’m particularly interested in the device reservation functionality. We’ve set up Google authentication for users, but it’s not entirely clear to me how to handle automation. We can issue a bearer token for an authenticated user and use it afterwards, but these tokens always have a limited lifetime. Is there a way to use OpenID authentication for automation?

Best regards,

Edward

UPD.

I see…

Note that you need to specify "ServiceAccount XYZ" in the Authorization header rather than "Bearer XYZ"

Turns out service accounts do work :slight_smile:

I was beginning to think that with OIDC authentication, other authentication methods wouldn’t work.