Not getting refresh token from userAuthorizedToken

#1

Dear team,

we have two different sets of APIs for login.

  1. Login with ABHA
  2. Login with mobile

If we try to login with ABHA and follow the below API sequence we were able to get the refresh token.

  1. /api/v2/auth/init
  2. /api/v2/auth/confirmWithMobileOTP

If we try to login with mobile and follow the below API sequence we were not able to get the refresh token

  1. /api/v2/registration/mobile/login/generateOtp
  2. api/v2/registration/mobile/login/verifyOtp
  3. api/v2/registration/mobile/login/userAuthorizedToken

Please advise us which APIs we need to call to make their behavior identical.

Thanks

#2

@IntegrationSupport Please advice us.

#3

Please send us error message that you are getting.

#4

@IntegrationSupport we are not receiving any error messages but responses are different.

/api/v2/auth/confirmWithMobileOTP
{
“token”: “eyJhbGciOiJSUzUxMiJ9.eyJzdWIiOiI5MS03NzgxLTYyMjUtMjEzNSIsImNsaWVudElkIjoiaGVhbHRoaWQtYXBpIiwic3lzdGVtIjoiQUJIQS1OIiwibW9iaWxlIjoiODQ2MDQ2MzUxMCIsImhlYWx0aElkIjoiZGhydXYyMzA5MTk5M0BzYngiLCJleHAiOjE2ODMwODg3NDYsImhlYWx0aElkTnVtYmVyIjoiOTEtNzc4MS02MjI1LTIxMzUiLCJpYXQiOjE2ODMwODY5NDZ9.dD7Mv8fW-2ViSjAIkRqQWJ1wrUlwN7J8NRAkfsD1XaxZU4WJpLoWLUzYnFc1vw0I9XRW2ins8Cl5IYcxb1o2Y7dYb7_4HAg8R5Opna1MQfiVkQPThHHFFKF0cIvJEZ_avZMcFoa7lK9bz0c46s9LPttC4QA_Ftjg_dFyVpqZfeaUpmLUtAaYSfLw57Y_oWJmdnYrqKC58yWZG6DNq5ue34RQmwpP2N5VHekfU3CnAkkFfFTZG91xNy-SsCM6toyKUV55Tsl9Nwgla51Sk8C6tAzZYTsuf2KcN353gkLt0qhfQWybdCxBvMFJRTMg7bqMCaM2R5ahYgYu208v4H_KHqWmZVpN8rWmhvFrRTcYUGsZPCb38WYzZT4YPEZGuutNoBKBdH1c3kh5wjmvha1o8bfXeyvq_skFVqtvtWg3jBo_i6vDa6uf4zJkAsWP4Q_eQiT4FxIjF9kwjHxIhpgccEpMLoj15dJ0quzQehU2AEzKH_9M2R3u4HBeVSoq9QGxJE44bMrNjVS7TsgTB0U85J9p2qCTzj5PA5Tp9cVzSr56h3-zIR1TcqmM5DGSD2rDcUL38L7U1RjlXpxHeyhEfmcqSTpXowEK7CsZn4TVHWjQ-oLV8odd7w_YF5pisxpTQWDE7Qem-2mOU4yYkQ-F-lkjDuzlHqh0CAS1amaXLsI”,
“expiresIn”: 1800,
“refreshToken”: “eyJhbGciOiJSUzUxMiJ9.eyJzdWIiOiI5MS03NzgxLTYyMjUtMjEzNSIsImNsaWVudElkIjoiaGVhbHRoaWQtYXBpIiwic3lzdGVtIjoiQUJIQS1OIiwidHlwIjoiUmVmcmVzaCIsImV4cCI6MTY4NDM4Mjk0NiwiaWF0IjoxNjgzMDg2OTQ2fQ.hf3pRrJ1fwf7t4H2PReC91FNhC9l1n3BF0fNHg3ksqt64gGlnaBak0AkFTFNhai76dubj_sKHDEy2zTN3VDCNZfqkOiPGiQCTZOqvhIsxi0lPOlT5Aw58tCzBrigYouxmXVzK1jqU_Fv5pnHiSBlzXgMAyrN1a0PmVQC8sljPhEckDoQK5efD62rtbdmEoQpOhL6l0mT1FYRgCXwly1SrW9l2rcpymCBDl7VbQ1_YfyvRZ1UNf7hoW8DIKIOOZHN9uzXQ2s5NKaHQ8wNu3-5zz2zlhfPpnYkResVzPydQi8lITDvJqffpPxPn4DjTvwHOJddyy6CVLSh4oY6kOXXv5K9c9CjYC0AqaZg-oA8rwVvo3Lq5pem2jMbIP4z11ZRz4wivh22Io7Ha__QSaVaOKda9loKanmFenVBvlZVhvrhT9KA85APi0k9qyJMeolko0pPasePTbkUB8Z7dkIkBA3Oqeq3JoB27qfzJoLdFhL01LyniDS0CQW-MQZI5Bd_6rJM4jwoUYd_Ip2b6Sn5YM1VbNWPoXeCEiTqIJ28Ya6XfGXHMoOT94WLPDuf4oou5mqOTBpIeOMRV4yCJerW-F3PEqJKImelvmV5c5q3u3mBbx-eCTf7NC4A4JDIFs4y__im7unazcsKqbhPj5fJ4fTIJIP0s9Q2sIteKnM7DGY”,
“refreshExpiresIn”: 1296000
}

/v2/registration/mobile/login/userAuthorizedToken
{
“token”: “eyJhbGciOiJSUzUxMiJ9.eyJzdWIiOiI5MS03NzgxLTYyMjUtMjEzNSIsImNsaWVudElkIjoiaGVhbHRoaWQtYXBpIiwic3lzdGVtIjoiQUJIQS1OIiwibW9iaWxlIjoiODQ2MDQ2MzUxMCIsImhlYWx0aElkIjoiZGhydXYyMzA5MTk5M0BzYngiLCJleHAiOjE2ODMwODgzMjMsImhlYWx0aElkTnVtYmVyIjoiOTEtNzc4MS02MjI1LTIxMzUiLCJpYXQiOjE2ODMwODY1MjN9.djjJ2cPtCG7NDsYLTQb_pEI706aKXVvcuHG5oRTJtFjhcbyCoXWuErZaG0cJlUtwK32TwLscwUchilYWr8LMQudyEZbL_FR3poHuAyBObpyDJUKB2VqEUoZbFpHdkkoqHTB8MX22xU5HkDfz4xq1pgSbamjSHl203Nn3Unw5-qKBvryq-vn7nPpTk3Y1cZnYahBo0PLXcMhI3LGUvTsk5SAa37-ubZg5NEF_dU6p3ulFCukdXykeDy5_aWjSc96zr6ZpR0KmrJPKpE8AEr9BwibvMYyhSlg1MIYZMh_0h-e06yb1GpyijXkKZU_O-IOzBeIfrfs3OGlRsGAZe4x3NdGuWm845YZnKC5uRH63SoHLAduyWiquEjbqlFM3f3yLH9rn6rGIiAO_zqjAsVoPxZewtwuGueDcnOyzyn7NA0TG32GLJpq4G9wDrnDhg4RgKEHLQXy64Qfp1PWBLiyG2WKbVJE3VJSJ7YWJ_AIU4_tJhaIZnbt9G1Qc0tOimswdhlQXg5UjLCkPg4HenqZrfm9_pZY9ikebIJRpuk3QF6Prmu_-EJLw2NZFfr41i25_u1P3trYdheAd_U9BTJUSJNhx98Gp0PxMBHkFoXDAgrOznb-aRTW9x1j1APwGgXwsZ_jfeAqg28ARJeretaFAdNLIsV5wO2dOMco3q_fI9rU”
}

#5

For API’s Login with mobile - Only access token generates in this flow.

#6

Yes, the question was why both login APIs have different response schema. From which API we can get a refresh token.