{"action":"created","issue":{"url":"https://api.github.com/repos/wildfly-security/wildfly-elytron/issues/1115","repository_url":"https://api.github.com/repos/wildfly-security/wildfly-elytron","labels_url":"https://api.github.com/repos/wildfly-security/wildfly-elytron/issues/1115/labels{/name}","comments_url":"https://api.github.com/repos/wildfly-security/wildfly-elytron/issues/1115/comments","events_url":"https://api.github.com/repos/wildfly-security/wildfly-elytron/issues/1115/events","html_url":"https://github.com/wildfly-security/wildfly-elytron/pull/1115","id":305983343,"number":1115,"title":"[ELY-1436] Log jdbc-realm key-mapper processing","user":{"login":"ivassile","id":2545122,"avatar_url":"https://avatars1.githubusercontent.com/u/2545122?v=4","gravatar_id":"","url":"https://api.github.com/users/ivassile","html_url":"https://github.com/ivassile","followers_url":"https://api.github.com/users/ivassile/followers","following_url":"https://api.github.com/users/ivassile/following{/other_user}","gists_url":"https://api.github.com/users/ivassile/gists{/gist_id}","starred_url":"https://api.github.com/users/ivassile/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ivassile/subscriptions","organizations_url":"https://api.github.com/users/ivassile/orgs","repos_url":"https://api.github.com/users/ivassile/repos","events_url":"https://api.github.com/users/ivassile/events{/privacy}","received_events_url":"https://api.github.com/users/ivassile/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2018-03-16T15:57:56Z","updated_at":"2018-03-22T13:41:26Z","closed_at":null,"author_association":"CONTRIBUTOR","pull_request":{"url":"https://api.github.com/repos/wildfly-security/wildfly-elytron/pulls/1115","html_url":"https://github.com/wildfly-security/wildfly-elytron/pull/1115","diff_url":"https://github.com/wildfly-security/wildfly-elytron/pull/1115.diff","patch_url":"https://github.com/wildfly-security/wildfly-elytron/pull/1115.patch"},"body":"wildfly-elytron: https://issues.jboss.org/browse/ELY-1436"},"comment":{"url":"https://api.github.com/repos/wildfly-security/wildfly-elytron/issues/comments/375309698","html_url":"https://github.com/wildfly-security/wildfly-elytron/pull/1115#issuecomment-375309698","issue_url":"https://api.github.com/repos/wildfly-security/wildfly-elytron/issues/1115","id":375309698,"user":{"login":"ivassile","id":2545122,"avatar_url":"https://avatars1.githubusercontent.com/u/2545122?v=4","gravatar_id":"","url":"https://api.github.com/users/ivassile","html_url":"https://github.com/ivassile","followers_url":"https://api.github.com/users/ivassile/followers","following_url":"https://api.github.com/users/ivassile/following{/other_user}","gists_url":"https://api.github.com/users/ivassile/gists{/gist_id}","starred_url":"https://api.github.com/users/ivassile/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ivassile/subscriptions","organizations_url":"https://api.github.com/users/ivassile/orgs","repos_url":"https://api.github.com/users/ivassile/repos","events_url":"https://api.github.com/users/ivassile/events{/privacy}","received_events_url":"https://api.github.com/users/ivassile/received_events","type":"User","site_admin":false},"created_at":"2018-03-22T13:41:26Z","updated_at":"2018-03-22T13:41:26Z","author_association":"CONTRIBUTOR","body":"@hkalina I've changed the trace log message, but I don't get your request to trace which algorithm was used. When the exception is thrown, identified != null which means that the algorithm is recognized by ModularCrypt and we don't use algorithm column value when ModularCrypt decodes. \r\n\r\nDo you think that it will help the user if we log a trace message with hash, salt, iterationCount and clear when constructing PasswordSpec object on line 272?"}}
{"actor":{"display_login":"ivassile"}}