Okay, I've narrowed it down to some pipeline groups not having the role permissions. As I look at my configuration, I have dozens or pipeline groups without role permissions that my api user has been able to schedule.
Questions: - Was there a bug maybe that was fixed that allowed a user to call the schedule api on a pipeline or pipeline group without needing at least "operator" permissions? - Is there a way to create/set role permissions on a pipeline group using the JSON config plugin? All my pipelines and pipeline groups are created via the JSON plugin. On Thu, Jan 7, 2021 at 11:18 AM Jeff <[email protected]> wrote: > I moved my server behind a load balancer/reverse proxy then upgraded from > 19.4.0 -> 20.4.0. > > I then did the database migration to Postgres then upgraded to 20.5.0 and > everything seemed to be working from the UI. > > I then upgraded to 20.10.0 and the UI, LDAP auth, etc. were all working > from the UI, but now that the server is back into our workflow, the API > call to schedule a pipeline is failing with 403. > > I am using basic auth. For the user, I was able to log into the UI > just fine. > > Did I miss a changelog on how access/authorization to the API is enabled? > > Thanks! > -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/CAPJK9%3DKfQgvZRieY%3DJvNM1%3DsKoYOKR3MgeY95Y1dS%2B29wtXTWg%40mail.gmail.com.
