{"action":"opened","issue":{"url":"https://api.github.com/repos/GreenPix/lycan/issues/29","repository_url":"https://api.github.com/repos/GreenPix/lycan","labels_url":"https://api.github.com/repos/GreenPix/lycan/issues/29/labels{/name}","comments_url":"https://api.github.com/repos/GreenPix/lycan/issues/29/comments","events_url":"https://api.github.com/repos/GreenPix/lycan/issues/29/events","html_url":"https://github.com/GreenPix/lycan/issues/29","id":192948508,"number":29,"title":"Authentication-less mode","user":{"login":"Vaelden","id":9787096,"avatar_url":"https://avatars.githubusercontent.com/u/9787096?v=3","gravatar_id":"","url":"https://api.github.com/users/Vaelden","html_url":"https://github.com/Vaelden","followers_url":"https://api.github.com/users/Vaelden/followers","following_url":"https://api.github.com/users/Vaelden/following{/other_user}","gists_url":"https://api.github.com/users/Vaelden/gists{/gist_id}","starred_url":"https://api.github.com/users/Vaelden/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Vaelden/subscriptions","organizations_url":"https://api.github.com/users/Vaelden/orgs","repos_url":"https://api.github.com/users/Vaelden/repos","events_url":"https://api.github.com/users/Vaelden/events{/privacy}","received_events_url":"https://api.github.com/users/Vaelden/received_events","type":"User","site_admin":false},"labels":[{"id":492681450,"url":"https://api.github.com/repos/GreenPix/lycan/labels/idea","name":"idea","color":"0052cc","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-12-01T20:05:44Z","updated_at":"2016-12-01T20:05:44Z","closed_at":null,"body":"Right now Lycan is always expecting proper authentication for clients, but at start-up inserts a few well-known values as valid playerId/token pairs.\r\n\r\nThis has a couple of limitations, such as not being able to connect twice with the same character without rebooting the server (which then makes it difficult to have a long-lived \"toy\" server)\r\n\r\nI was thinking about adding a command-line parameter that would disable authentication checks, and accept the connection even when the token is incorrect.\r\n\r\nAn alternative could be to make clients aware of the management API (which would then need to be accessible from all clients, which may not be trivial), and make them add their own tokens before attempting to connect.\r\n\r\nIn either case, we may need to implement checks in Lycan to avoid 2 players connecting with the same UUID (although depending on how clients are implemented, the likelihood of generating randomly the same UUID twice is negligible)."}}
{"actor":{"display_login":"Vaelden"}}