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%3D%2BWbA_zDbLRhtJhUzadtLuEDh%2BN38Xn65ig-5fhpM6UkQ%40mail.gmail.com.
