iftomkins

Hi iftomkins

this only applies if you are using the "Fallback SSO" option in your Lithium SSO implementation. You can see what the "Fallback" flow is in the  diagram attached at the end of the KB article.

If your implementation supports the fallback flow (via the query parameter), then you can enable / disable the "auto login" functionality (can be seen here) for that flow via the checkbox.

I hope this clarifies it!

Hi iftomkins

Looks good, however I'd recommend wrapping in <attempt> tags to catch any errors should something go wrong. It is highly unlikely as this is fairly simple logic however this should cover most scenarios.

<#attempt>
<#if messageAuthorId == -1 >
    <#assign avatarUrl = "/html/assets/icon_anonymous_message.png" />
<#else>
    <#assign avatarUrl = rest("/users/id/${messageAuthorId}/profiles/avatar/url").value />
</#if>
<#recover>
    <!-- what to do if the above logic fails or there is an error -->
    <#assign avatarUrl = "/html/assets/icon_anonymous_message.png" />
</#attempt>

Wrapping in this around your code will catch any exceptions in the code should they occurr and instead of displaying the error it'll default to the anonymous user avatar you have specified.

hi iftomkins

Afraid it's not possible. if I understand correctly, the browser will not send the URL fragment to server

Here's a quote from:

https://blog.httpwatch.com/2011/03/01/6-things-you-should-know-about-fragment-urls/

"

2. Fragments Are not Sent in HTTP Request Messages

If you try using fragment URLs in an HTTP sniffer like HttpWatch, you’ll never see the fragment IDs in the requested URL or Referer header. The reason is that the fragment identifier is only used by the browser – it doesn’t affect which resource is returned from the server.

"

Since the Server never gets the URL fragment ID, it will not be able to redirect with any fragment ID