• Icon: Bug Bug
    • Resolution: Not a bug
    • Icon: Low Low
    • None
    • 4.3.0
    • REST
    • None

      Issue Summary

      When using command line, REST API endpoints may fail with an "Application failed to authenticate" error.

      Steps to Reproduce

      The following REST API calls (at least) fail to be executed:

      fkraemer@C02ZX4MTMD6N ~ % curl -u fkraemer -X GET "http://localhost:8095/crowd/rest/usermanagement/1/user/attribute?username=crowd1"
      Enter host password for user 'fkraemer':
      Application failed to authenticate
      fkraemer@C02ZX4MTMD6N ~ % curl -u fkraemer -X PUT -d '{"value":"newpwd"}' "http://localhost:8095/crowd/rest/usermanagement/1/user/password?username=crowd1"
      Enter host password for user 'fkraemer':
      Application failed to authenticate
      fkraemer@C02ZX4MTMD6N ~ %
      

      Notes:

      • Authentication of fkraemer works directly in the browser.
      • The base URL http://localhost:8095/crowd is correct.
      • The user fkraemer is a local Crowd administrator.
      • The user crowd1 is a local Crowd regular user.

      Expected Results

      Authentication works and the REST API call is executed successfully.

      Actual Results

      Authentication fails and the REST API call is not executed.

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available.

            [CWD-5741] REST API authentication fails

            Pawel Gruszczynski (Inactive) made changes -
            Comment [ Please note that you're using an endpoint dedicated for applications and should authenticate with application credentials, not user credentials. ]
            Pawel Gruszczynski (Inactive) made changes -
            Resolution New: Not a bug [ 12 ]
            Status Original: Needs Triage [ 10030 ] New: Closed [ 6 ]
            Bugfix Automation Bot made changes -
            Support reference count New: 1
            Felipe Kraemer made changes -
            Description Original: h3. Issue Summary

            When using command line, REST API endpoints may fail with an "Application failed to authenticate" error.
            h3. Steps to Reproduce
            The following REST API calls (at least) fail to be executed:
            {code}
            fkraemer@C02ZX4MTMD6N ~ % curl -u fkraemer -X GET "http://localhost:8095/crowd/rest/usermanagement/1/user/attribute?username=crowd1"
            Enter host password for user 'fkraemer':
            Application failed to authenticate
            fkraemer@C02ZX4MTMD6N ~ % curl -u fkraemer -X PUT -d '{"value":"newpwd"}' "http://localhost:8095/crowd/rest/usermanagement/1/user/password?username=crowd1"
            Enter host password for user 'fkraemer':
            Application failed to authenticate
            fkraemer@C02ZX4MTMD6N ~ %
            {code}
            *Notes:*
            * Authentication of {{fkraemer}} works directly in the browser.
            * The user {{fkraemer}} is an administrator.
            * The base URL {{http://localhost:8095/crowd}} is correct.
            * The user {{crowd1}} exists and is local to Crowd.

            h3. Expected Results
            Authentication works and the REST API call is executed successfully.

            h3. Actual Results
            Authentication fails and the REST API call is not executed.

            h3. Workaround
            Currently there is no known workaround for this behavior. A workaround will be added here when available.
            New: h3. Issue Summary

            When using command line, REST API endpoints may fail with an "Application failed to authenticate" error.
            h3. Steps to Reproduce

            The following REST API calls (at least) fail to be executed:
            {code:java}
            fkraemer@C02ZX4MTMD6N ~ % curl -u fkraemer -X GET "http://localhost:8095/crowd/rest/usermanagement/1/user/attribute?username=crowd1"
            Enter host password for user 'fkraemer':
            Application failed to authenticate
            fkraemer@C02ZX4MTMD6N ~ % curl -u fkraemer -X PUT -d '{"value":"newpwd"}' "http://localhost:8095/crowd/rest/usermanagement/1/user/password?username=crowd1"
            Enter host password for user 'fkraemer':
            Application failed to authenticate
            fkraemer@C02ZX4MTMD6N ~ %
            {code}
            *Notes:*
             * Authentication of {{fkraemer}} works directly in the browser.
             * The base URL {{[http://localhost:8095/crowd]}} is correct.
             * The user {{fkraemer}} is a local Crowd administrator.
             * The user {{crowd1}} is a local Crowd regular user.

            h3. Expected Results

            Authentication works and the REST API call is executed successfully.
            h3. Actual Results

            Authentication fails and the REST API call is not executed.
            h3. Workaround

            Currently there is no known workaround for this behavior. A workaround will be added here when available.
            Felipe Kraemer made changes -
            Description Original: h3. Issue Summary

            When using command line, REST API endpoints may fail with an "Application failed to authenticate" error.
            h3. Steps to Reproduce
            The following REST API calls (at least) fail to be executed:
            {code}
            fkraemer@C02ZX4MTMD6N ~ % curl -u fkraemer -X GET "http://localhost:8095/crowd/rest/usermanagement/1/user/attribute?username=crowd1"
            Enter host password for user 'fkraemer':
            Application failed to authenticate
            fkraemer@C02ZX4MTMD6N ~ % curl -u fkraemer -X PUT -d '{"value":"newpwd"}' "http://localhost:8095/crowd/rest/usermanagement/1/user/password?username=crowd1"
            Enter host password for user 'fkraemer':
            Application failed to authenticate
            fkraemer@C02ZX4MTMD6N ~ %

            *Notes:*
            * Authentication of {{fkraemer}} works directly in the browser.
            * The user {{fkraemer}} is an administrator.
            * The base URL {{http://localhost:8095/crowd}} is correct.
            * The user {{crowd1}} exists and is local to Crowd.

            h3. Expected Results
            Authentication works and the REST API call is executed successfully.

            h3. Actual Results
            Authentication fails and the REST API call is not executed.

            h3. Workaround
            Currently there is no known workaround for this behavior. A workaround will be added here when available.
            New: h3. Issue Summary

            When using command line, REST API endpoints may fail with an "Application failed to authenticate" error.
            h3. Steps to Reproduce
            The following REST API calls (at least) fail to be executed:
            {code}
            fkraemer@C02ZX4MTMD6N ~ % curl -u fkraemer -X GET "http://localhost:8095/crowd/rest/usermanagement/1/user/attribute?username=crowd1"
            Enter host password for user 'fkraemer':
            Application failed to authenticate
            fkraemer@C02ZX4MTMD6N ~ % curl -u fkraemer -X PUT -d '{"value":"newpwd"}' "http://localhost:8095/crowd/rest/usermanagement/1/user/password?username=crowd1"
            Enter host password for user 'fkraemer':
            Application failed to authenticate
            fkraemer@C02ZX4MTMD6N ~ %
            {code}
            *Notes:*
            * Authentication of {{fkraemer}} works directly in the browser.
            * The user {{fkraemer}} is an administrator.
            * The base URL {{http://localhost:8095/crowd}} is correct.
            * The user {{crowd1}} exists and is local to Crowd.

            h3. Expected Results
            Authentication works and the REST API call is executed successfully.

            h3. Actual Results
            Authentication fails and the REST API call is not executed.

            h3. Workaround
            Currently there is no known workaround for this behavior. A workaround will be added here when available.
            Felipe Kraemer created issue -

              Unassigned Unassigned
              fkraemer Felipe Kraemer
              Affected customers:
              1 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: