# ACS discussion ## July 14 Focus on Pulp 3. * does the rhui have any own implementation/workaround? Any planning with Pulp3? * use cases * who is going to use it? * and how? * How it is designed? * acs will be used automatically and always if exists * certs and others is solved by one remote (which will be base path for ACS) * plugins that doesn't use this feature won't be affected by any processing * how the certs will be delivered from RHUI * old way: * rpm generated * RHUI - token (header) are valid short time * non-production rhui needs only two headers + certs * production - there is constantly changing pieces we need to keep eye on ## Links * https://hackmd.io/nb83kPmTTgayxEq7jn1N6w?view * design doc * https://pulp.plan.io/issues/7832 * epic issue * https://access.redhat.com/articles/1531833