# Integrate discourse authentication with external service which is token base authentication

**URL:** <https://meta.discourse.org/t/integrate-discourse-authentication-with-external-service-which-is-token-base-authentication/83448>\
**Category:** SSO\
**Created:** [March 21, 2018, 1:53am UTC](https://meta.discourse.org/t/integrate-discourse-authentication-with-external-service-which-is-token-base-authentication/83448 "2018-03-21T01:53:37Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![cwilson](https://avatars.discourse-cdn.com/v4/letter/c/f08c70/32.png) [@cwilson](https://meta.discourse.org/u/cwilson)\
**Post date:** [October 24, 2018, 4:27pm UTC](https://meta.discourse.org/t/integrate-discourse-authentication-with-external-service-which-is-token-base-authentication/83448/3 "2018-10-24T16:27:04Z")

</div>

Same here.

One possible solution that seems straightforward: Is there a way to pass custom query parameters to the Discourse site’s `/session/sso` endpoint to allow additional data to be added to the payload passed through the SSO system? If so, the token could be passed through successfully using something like:

`https://mydiscoursesite.mydomain.com/session/sso?token=abc123`

(I should say I tried the above, but the extra parameter was not incorporated into the SSO payload.)

---

_[View the full topic](https://meta.discourse.org/t/integrate-discourse-authentication-with-external-service-which-is-token-base-authentication/83448)._