<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">IMHO, the simplest thing to do would be to configure an haproxy for https, same as now. But pre-load some mappings in haproxy - something like:<div> <a href="https://dev.foo.com/bob1">https://dev.foo.com/bob1</a> ==> <a href="http://bob.foo.com">bob.foo.com</a>:9001<br> <a href="https://dev.foo.com/bob">https://dev.foo.com/bob</a>2 ==> <a href="http://bob.foo.com:8080">bob.foo.com:</a>9002</div> <a href="https://dev.foo.com/bob1">https://dev.foo.com/doug1</a> ==> <a href="http://bob.foo.com">doug.foo.com</a>:9001<div> <a href="https://dev.foo.com/bob1">https://dev.foo.com/doug</a>2 ==> <a href="http://doug.foo.com:9002">doug.foo.com:9002</a></div><div><br></div><div>Developer Bob would run their dev Seaside listening on porto 9001 on their workstation. Configuring extra paths/portnos mappings would allow development of more than one web server at the same time.</div><div><br></div><div>If you did manage to get https to work directly from GemStone, then that configuration would actually be further away from the actual production deployment.</div><div><br></div><div>Just occurred to me that maybe Azure SSO might not be able to handle the situation, but I don’t know Azure.</div><div><br></div><div>HTH</div><div>Yanni</div><div><br><div><blockquote type="cite"><div>On Jan 11, 2024, at 2:31 PM, Bob Nemec via Glass <glass@lists.gemtalksystems.com> wrote:</div><br class="Apple-interchange-newline"><div><div><div class="yahoo-style-wrap" style="font-family:lucida console, sans-serif;font-size:13px;"><div dir="ltr" data-setdir="false">Hello,</div><div dir="ltr" data-setdir="false">I'm an trying to implement an Azure implicit grant workflow for our small development model GS database. </div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">Normally, we start a pool of web gems with HAProxy as the reverse proxy, which gives us https access and allows for Azure single sign-on authentication. For the small development databases we run one web gem and connect on a known port. Works fine for development work, but it does not support single sign-on since Azure only allow for https (or http for localhost) in its redirect setting. </div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">So, how can I start a single Seaside web gem that accepts a https connection? </div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">Thanks, </div><div dir="ltr" data-setdir="false">Bob Nemec</div><div dir="ltr" data-setdir="false"><br></div></div></div>_______________________________________________<br>Glass mailing list<br>Glass@lists.gemtalksystems.com<br>https://lists.gemtalksystems.com/mailman/listinfo/glass<br></div></blockquote></div><br></div></body></html>