<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi James,<div class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 5 Jun 2020, at 03:23, Manger, James <<a href="mailto:James.H.Manger@team.telstra.com" class="">James.H.Manger@team.telstra.com</a>> wrote:</div><div class=""><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class="">If you merely want to trigger a different look-n-feel, define a “brand” parameter to add the to the authorization request.<o:p class=""></o:p></span></div></div></div></blockquote></div><br class=""></div><div class="">Unfortunately this doesn’t work when the authorization endpoint is a claimed https url for a mobile app: the mobile app to be used is selected purely based on the host/path segment.</div><div class=""><br class=""></div><div class="">Joseph</div><div class=""><br class=""></div></body></html>