title: Linkedin OAuth2.0 : How to configure OAuth 2.0 Redirect URL with a wildcard subdomain url for a multi tenant application
body: <p>I am trying to configure a LinkedIn application for a multi tenant site. I will have 20+ tenants using the same application and the number is going to increase every time.</p>
  
  <p>As per Linkedin API documentation (<a href="https://developer.linkedin.com/docs/oauth2" rel="noreferrer">https://developer.linkedin.com/docs/oauth2</a>) we need to ensure following points</p>
  
  <ol>
  <li><p><em>We strongly recommend using HTTPS whenever possible</em> </p></li>
  <li><p><em>URLs must be
  absolute (e.g. "<a href="https://example.com/auth/callback" rel="noreferrer">https://example.com/auth/callback</a>", not
  "/auth/callback")</em> </p></li>
  <li><p><em>URL arguments are ignored (i.e.
  <a href="https://example.com/?id=1" rel="noreferrer">https://example.com/?id=1</a> is the same as <a href="https://example.com/" rel="noreferrer">https://example.com/</a>)</em> </p></li>
  <li><em>URLs
  cannot include #'s (i.e.
  "<a href="https://example.com/auth/callback#linkedin" rel="noreferrer">https://example.com/auth/callback#linkedin</a>" is invalid)</em></li>
  </ol>
  
  <p>Can i configure redirect url as <a href="https://*.mysite.com/auth/linkedin/callback" rel="noreferrer">https://*.mysite.com/auth/linkedin/callback</a> instead of specifying url of each tenant separately.</p>