{"action":"opened","issue":{"url":"https://api.github.com/repos/pingidentity/mod_auth_openidc/issues/190","repository_url":"https://api.github.com/repos/pingidentity/mod_auth_openidc","labels_url":"https://api.github.com/repos/pingidentity/mod_auth_openidc/issues/190/labels{/name}","comments_url":"https://api.github.com/repos/pingidentity/mod_auth_openidc/issues/190/comments","events_url":"https://api.github.com/repos/pingidentity/mod_auth_openidc/issues/190/events","html_url":"https://github.com/pingidentity/mod_auth_openidc/issues/190","id":186398459,"number":190,"title":"Trying to implement a custom OP Discovery page","user":{"login":"anthnd","id":15786604,"avatar_url":"https://avatars.githubusercontent.com/u/15786604?v=3","gravatar_id":"","url":"https://api.github.com/users/anthnd","html_url":"https://github.com/anthnd","followers_url":"https://api.github.com/users/anthnd/followers","following_url":"https://api.github.com/users/anthnd/following{/other_user}","gists_url":"https://api.github.com/users/anthnd/gists{/gist_id}","starred_url":"https://api.github.com/users/anthnd/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/anthnd/subscriptions","organizations_url":"https://api.github.com/users/anthnd/orgs","repos_url":"https://api.github.com/users/anthnd/repos","events_url":"https://api.github.com/users/anthnd/events{/privacy}","received_events_url":"https://api.github.com/users/anthnd/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-10-31T21:10:06Z","updated_at":"2016-10-31T21:10:06Z","closed_at":null,"body":"Hello,\r\nI'm trying to integrate OpenID Connect into Request Tracker (an email ticket tracking system) for my work, but I'm having some problems with providing the right login setup that I planned on integrating.\r\nRequest Tracker already has its own login system and I'm building OpenID Connect on top of it. It has a built-in feature to authenticate users based on comparing the value set for REMOTE_USER to its internal database of users. What I want is for when users visit the RT Login page, they also have an option to use Google Sign In - for example. Customizing the RT login page is a trivial matter so providing the front-end sugar is no problem. What I'm having a problem with are the things going on in the background.\r\n\r\nHere's my openidc.conf file for reference - it's pretty minimal since my knowledge of Apache configuration is still rather limited:\r\n\r\n```\r\nOIDCMetadataDir /opt/software/rt/etc/OIDCMetadata\r\n\r\nOIDCRedirectURI http://localhost/oauth2callback\r\nOIDCCryptoPassphrase password\r\n\r\nOIDCRemoteUserClaim email\r\nOIDCScope \"email\"\r\n\r\n<Location />\r\n    AuthType openid-connect\r\n    Require valid-user\r\n    LogLevel debug\r\n</Location>\r\n```\r\n\r\nWith this set up, when I go to localhost, I get the nice and ugly default OP Discovery page, but it serves its purpose exactly as I want EXCEPT for the fact that I can't use Request Tracker's login system.\r\nSo I looked into an external discovery page using OIDCDiscoverURL, but from what I understand, this is an external page that basically has no relation to the original website?\r\nWhat I want to implement is a custom discovery page **on localhost**. Where I can set up the default login and throw in the appropriate links for other sign in options. I've tried many variations of my config and I'm still stuck with this problem in one way or another.\r\nThis seems like something that should surely be fairly simple to set up, but I just can't figure it out.\r\n\r\nI would appreciate any help to get me going."}}
{"actor":{"display_login":"anthnd"}}