[13:24:02 CST(-0600)] <dmccallum54> i'm looking at a situation where someone wants to deliver uportal via an iframe in another app

[13:24:32 CST(-0600)] <dmccallum54> it works fine, but they'd like to be able to output the UI with a different skin or possibly theme when the UI is being delivered in this way

[13:24:59 CST(-0600)] <dmccallum54> i see that the uP login process can accept a profile key as a request param, which would then let me switch to a different theme

[13:25:33 CST(-0600)] <dmccallum54> is there something OOTB, though, that would let the preferred profile be set on the URL, period?

[13:26:09 CST(-0600)] <dmccallum54> e.g. set the iframe to https://domain.edu/portal?profile=embedded

[13:28:52 CST(-0600)] <dmccallum54> i see the user agent profile mapping mechanism and the session-based mapping mechanism. just wondering if there's another OOTB strategy that would accept the profile key from a URL and remember it long enough to survive login redirects

[13:30:03 CST(-0600)] <jwennmacher1> Not that I can think of. You could add something along the lines of what you've already identified (and it would be a welcome addition)

[14:06:33 CST(-0600)] <jwennmacher1> tlev: I'll take care of https://github.com/Jasig/uPortal/pull/177/commits since I can see their repo

[14:06:49 CST(-0600)] <tlev> ah, is that it, gotcha thanks!

[16:41:32 CST(-0600)] <tlev> I just noticed that we will have to cut a release of resource server to get bootstrap 3.0 in it. rs v1.0.31 only has 2.3. You can switch to snapshot for rs if you want this to work in the mean time.

[16:42:27 CST(-0600)] <tlev> I've also made a note in the pull request for bootstrap 3

[16:47:58 CST(-0600)] <jwennmacher1> Thanks. Sorry about that .. I meant to test it after merging the pull request but got pulled into an issue

Browser not supported