{"action":"opened","issue":{"url":"https://api.github.com/repos/helm/charts/issues/6851","repository_url":"https://api.github.com/repos/helm/charts","labels_url":"https://api.github.com/repos/helm/charts/issues/6851/labels{/name}","comments_url":"https://api.github.com/repos/helm/charts/issues/6851/comments","events_url":"https://api.github.com/repos/helm/charts/issues/6851/events","html_url":"https://github.com/helm/charts/issues/6851","id":345069266,"node_id":"MDU6SXNzdWUzNDUwNjkyNjY=","number":6851,"title":"Default install of Keycloak does not allow login.","user":{"login":"YenTheFirst","id":444387,"node_id":"MDQ6VXNlcjQ0NDM4Nw==","avatar_url":"https://avatars3.githubusercontent.com/u/444387?v=4","gravatar_id":"","url":"https://api.github.com/users/YenTheFirst","html_url":"https://github.com/YenTheFirst","followers_url":"https://api.github.com/users/YenTheFirst/followers","following_url":"https://api.github.com/users/YenTheFirst/following{/other_user}","gists_url":"https://api.github.com/users/YenTheFirst/gists{/gist_id}","starred_url":"https://api.github.com/users/YenTheFirst/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/YenTheFirst/subscriptions","organizations_url":"https://api.github.com/users/YenTheFirst/orgs","repos_url":"https://api.github.com/users/YenTheFirst/repos","events_url":"https://api.github.com/users/YenTheFirst/events{/privacy}","received_events_url":"https://api.github.com/users/YenTheFirst/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-07-27T02:33:42Z","updated_at":"2018-07-27T02:33:42Z","closed_at":null,"author_association":"NONE","body":"<!-- Thanks for filing an issue! Before hitting the button, please answer these questions. It's helpful to search the existing GitHub issues first. It's likely that another user has already reported the issue you're facing, or it's a known issue that we're already aware of-->\r\n\r\n**Is this a request for help?**: No\r\n\r\n---\r\n\r\n**Is this a BUG REPORT or FEATURE REQUEST?** (choose one): Bug Report\r\n\r\n<!--\r\nIf this is a BUG REPORT, please:\r\n  - Fill in as much of the template below as you can.  If you leave out\r\n    information, we can't help you as well.\r\n\r\nIf this is a FEATURE REQUEST, please:\r\n  - Describe *in detail* the feature/behavior/change you'd like to see.\r\n\r\nIn both cases, be ready for followup questions, and please respond in a timely\r\nmanner.  If we can't reproduce a bug or think a feature already exists, we\r\nmight close your issue.  If we're wrong, PLEASE feel free to reopen it and\r\nexplain why.\r\n-->\r\n\r\n**Version of Helm and Kubernetes**: \r\nHelm v2.9.1\r\nKubernetes 1.9.9\r\n\r\n**Which chart**:\r\nstable/keycloak\r\n\r\n**What happened**:\r\nIt generates a service which only exposes access over HTTP, while Keycloak's default behavior is to require SSL for all external requests. This causes all attempted logins to fail.\r\n\r\n**What you expected to happen**:\r\nI'm able to log in.\r\n\r\n**How to reproduce it** (as minimally and precisely as possible):\r\nthe commands:\r\n```\r\nhelm install stable/keycloak --name test-keycloak\r\nhelm test test-keycloak\r\nkubectl logs test-keycloak-0 | tail -n1\r\n```\r\nresult in the output:\r\n```\r\nRUNNING: test-keycloak-test\r\nFAILED: test-keycloak-test, run `kubectl logs test-keycloak-test --namespace default` for more info\r\nError: 1 test(s) failed\r\n02:26:29,528 WARN  [org.keycloak.events] (default task-42) type=LOGIN_ERROR, realmId=master, clientId=null, userId=null, ipAddress=100.118.144.66, error=ssl_required\r\n```\r\n\r\nAdditionally, navigating in a browser to the given URL for accessing the installed service, and clicking on the \"Administration Console\" link, leads to a page that says \"We're sorry, HTTPS required\"\r\n\r\n**Anything else we need to know**:\r\nAs an additional complication to only exposing the service over HTTP - if this server is presented to the outside world through an nginx-ingress which is terminating SSL, the redirect URIs it generates will be prefixed with `http://`, not `https://`, which causes configuration problems with most oauth identity providers."}}
{"actor":{"display_login":"YenTheFirst"}}