When upgrading from GCS with myproxy-oauth-0.25-1.el7+gt6.noarch or prior to myproxy-oauth-0.26-1.el7+gt6.noarch, the /etc/httpd/conf.d/wsgi-myproxy-oauth.conf file gets deleted thus breaking the MyProxy OAuth Delegation Service. The file can be recreated by running 'globus-connect-server-setup' again, but this requires intervention by the GCS admin. Reproduced by installing GCS with myproxy-oauth-0.25-1.el7+gt6.noarch on CentOS 7, configuring endpoint for OAuth based activation, and then updating to myproxy-oauth-0.26-1.el7+gt6.noarch.
In my case running globus-connect-server-id-setup --verbose --force did not recreate the missing file. Because my systems separate ID from IO, the globus-connect-server-setup command is not installed.
When upgrading from GCS with myproxy-oauth-0.25-1.el7+gt6.noarch or prior to myproxy-oauth-0.26-1.el7+gt6.noarch, the /etc/httpd/conf.d/wsgi-myproxy-oauth.conf file gets deleted thus breaking the MyProxy OAuth Delegation Service. The file can be recreated by running 'globus-connect-server-setup' again, but this requires intervention by the GCS admin. Reproduced by installing GCS with myproxy-oauth-0.25-1.el7+gt6.noarch on CentOS 7, configuring endpoint for OAuth based activation, and then updating to myproxy-oauth-0.26-1.el7+gt6.noarch.
See also these tickets:
https://globusonline.zendesk.com/agent/tickets/308775 https://globusonline.zendesk.com/agent/tickets/308816