https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/AAA-75 aaa <p>When doing the following curl (which used to work), authentication fails.</p> <p>curl -k -X POST -H "Content-Type: application/x-www-form-urlencoded" <a href="http://127.0.0.1:8181/oauth2/token" class="external-link" target="_blank" rel="nofollow noopener">http://127.0.0.1:8181/oauth2/token</a> -d "grant_type=password&amp;username=admin&amp;password=admin&amp;scope=sdn"​</p> <p>the response is:</p> {"error":"Domain :sdn\u200b does not exist"} <p>Operating System: All<br/> Platform: All</p> AAA-75

domain contains garbage characters when authenticating

Improvement Confirmed Unresolved Unassigned Sharon Aicler Tue, 8 Dec 2015 17:28:59 +0000 Tue, 3 Oct 2023 13:20:35 +0000 General 0 2 <p>Try the following instead:</p> <p>curl -k -X POST -H "Content-Type: application/json" <a href="http://127.0.0.1:8181/oauth2/token" class="external-link" target="_blank" rel="nofollow noopener">http://127.0.0.1:8181/oauth2/token</a> -d "grant_type=password&amp;username=admin&amp;password=admin&amp;scope=sdn"​</p> <p>The above works for me.</p> <p>Works when "application/json" header is used.</p> <p>&gt; "grant_type=password&amp;username=admin&amp;password=admin&amp;scope=sdn"​</p> <p>That is not a string containing JSON encoded object. But it is an URL-encoded www form.<br/> I wonder why user has to specify invalid content-type to get correct behavior.</p> <p>I am not the original author of this code; they have long since left this project. I received documentation concerning use of the token endpoint, and that always mentioned using the application/json content type; However, that does not mean it is right... let me take a closer look by reopening and taking this one.</p> <p>TokenEndpoint is the backing HttpServlet implementation for the /oauth2/token endpoint. It looks like whoever wrote the Java code assumed the payload would be in a certain format (incorrectly). We can use this bug to track it... my guess is this has been an issue for a very long time and people just accepted it in its broken form.</p> <p>Workaround for when this happens; delete idmlight.db.* and restart karaf. Working on the proper fix though.</p> <p>De-escalating since a workaround exists.</p> Cloners AAA-157 Development External issue ID 4742 External issue URL Rank 0|hzzztr: