API authentication procedure using tokens and session token












0















I am using a web service that uses the following authentication process for the API calls.




  1. POST to fqdn/login_users with Basic Auth "user name, password" (https of course)
    returns a (rather long) token.


  2. POST to fqdn/users/login with the header Authorization Token token=
    returns a different user name, (short) session token with bunch of other informational stuff like last login time, validity period etc.


  3. API calls using the returned user name and session token in Basic Auth header.



I am trying to understand the rationale behind this approach.




  1. First of all this is a common pattern used in API authentication ?


  2. Instead of the two step process why not return the session token as a response for the first "login_users" API ?


  3. Instead of using the original user id why return a different user id in the 2nd step and use that in the subsequent API calls ?











share|improve this question



























    0















    I am using a web service that uses the following authentication process for the API calls.




    1. POST to fqdn/login_users with Basic Auth "user name, password" (https of course)
      returns a (rather long) token.


    2. POST to fqdn/users/login with the header Authorization Token token=
      returns a different user name, (short) session token with bunch of other informational stuff like last login time, validity period etc.


    3. API calls using the returned user name and session token in Basic Auth header.



    I am trying to understand the rationale behind this approach.




    1. First of all this is a common pattern used in API authentication ?


    2. Instead of the two step process why not return the session token as a response for the first "login_users" API ?


    3. Instead of using the original user id why return a different user id in the 2nd step and use that in the subsequent API calls ?











    share|improve this question

























      0












      0








      0








      I am using a web service that uses the following authentication process for the API calls.




      1. POST to fqdn/login_users with Basic Auth "user name, password" (https of course)
        returns a (rather long) token.


      2. POST to fqdn/users/login with the header Authorization Token token=
        returns a different user name, (short) session token with bunch of other informational stuff like last login time, validity period etc.


      3. API calls using the returned user name and session token in Basic Auth header.



      I am trying to understand the rationale behind this approach.




      1. First of all this is a common pattern used in API authentication ?


      2. Instead of the two step process why not return the session token as a response for the first "login_users" API ?


      3. Instead of using the original user id why return a different user id in the 2nd step and use that in the subsequent API calls ?











      share|improve this question














      I am using a web service that uses the following authentication process for the API calls.




      1. POST to fqdn/login_users with Basic Auth "user name, password" (https of course)
        returns a (rather long) token.


      2. POST to fqdn/users/login with the header Authorization Token token=
        returns a different user name, (short) session token with bunch of other informational stuff like last login time, validity period etc.


      3. API calls using the returned user name and session token in Basic Auth header.



      I am trying to understand the rationale behind this approach.




      1. First of all this is a common pattern used in API authentication ?


      2. Instead of the two step process why not return the session token as a response for the first "login_users" API ?


      3. Instead of using the original user id why return a different user id in the 2nd step and use that in the subsequent API calls ?








      api authentication jwt basic-authentication






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 20 '18 at 21:04









      ManoharManohar

      1,39172746




      1,39172746
























          0






          active

          oldest

          votes











          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53401509%2fapi-authentication-procedure-using-tokens-and-session-token%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53401509%2fapi-authentication-procedure-using-tokens-and-session-token%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          "Incorrect syntax near the keyword 'ON'. (on update cascade, on delete cascade,)

          Alcedinidae

          Origin of the phrase “under your belt”?