{"action":"created","issue":{"url":"https://api.github.com/repos/jwtk/jjwt/issues/47","labels_url":"https://api.github.com/repos/jwtk/jjwt/issues/47/labels{/name}","comments_url":"https://api.github.com/repos/jwtk/jjwt/issues/47/comments","events_url":"https://api.github.com/repos/jwtk/jjwt/issues/47/events","html_url":"https://github.com/jwtk/jjwt/issues/47","id":106001617,"number":47,"title":"Possibility to force signature algorithm on parse","user":{"login":"danilobuerger","id":996231,"avatar_url":"https://avatars.githubusercontent.com/u/996231?v=3","gravatar_id":"","url":"https://api.github.com/users/danilobuerger","html_url":"https://github.com/danilobuerger","followers_url":"https://api.github.com/users/danilobuerger/followers","following_url":"https://api.github.com/users/danilobuerger/following{/other_user}","gists_url":"https://api.github.com/users/danilobuerger/gists{/gist_id}","starred_url":"https://api.github.com/users/danilobuerger/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/danilobuerger/subscriptions","organizations_url":"https://api.github.com/users/danilobuerger/orgs","repos_url":"https://api.github.com/users/danilobuerger/repos","events_url":"https://api.github.com/users/danilobuerger/events{/privacy}","received_events_url":"https://api.github.com/users/danilobuerger/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":7,"created_at":"2015-09-11T12:37:11Z","updated_at":"2015-09-11T17:59:15Z","closed_at":null,"body":"Is it possible to force the signature algorithm on parse? Meaning that the jwt is only considered valid if it is signed with a particular algorithm?\r\n\r\nIf not, is it possible to disallow the NONE algorithm or otherwise check the algorithm and make sure that the jwt is signed on parse?"},"comment":{"url":"https://api.github.com/repos/jwtk/jjwt/issues/comments/139613719","html_url":"https://github.com/jwtk/jjwt/issues/47#issuecomment-139613719","issue_url":"https://api.github.com/repos/jwtk/jjwt/issues/47","id":139613719,"user":{"login":"lhazlewood","id":121180,"avatar_url":"https://avatars.githubusercontent.com/u/121180?v=3","gravatar_id":"","url":"https://api.github.com/users/lhazlewood","html_url":"https://github.com/lhazlewood","followers_url":"https://api.github.com/users/lhazlewood/followers","following_url":"https://api.github.com/users/lhazlewood/following{/other_user}","gists_url":"https://api.github.com/users/lhazlewood/gists{/gist_id}","starred_url":"https://api.github.com/users/lhazlewood/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/lhazlewood/subscriptions","organizations_url":"https://api.github.com/users/lhazlewood/orgs","repos_url":"https://api.github.com/users/lhazlewood/repos","events_url":"https://api.github.com/users/lhazlewood/events{/privacy}","received_events_url":"https://api.github.com/users/lhazlewood/received_events","type":"User","site_admin":false},"created_at":"2015-09-11T17:59:15Z","updated_at":"2015-09-11T17:59:15Z","body":"This is documented in the Readme:\r\n\r\n> Known Type convenience parse methods\r\n>\r\n> If, unlike above, you are confident of the compact string format and know which type of JWT or JWS it will produce, you can just use one of the 4 new convenience parsing methods to get exactly the type of JWT or JWS you know exists.\r\n\r\nIs this issue resolved, then, by just improving the documentation?"}}