NoSuchFlowExecutionException with office365 apps

[privas]

Hey guys,

Are we referring to a node as a shibboleth instance? I do have two cas portal/shibboleth servers behind a loadbalancer. I'm noticing these errors only appear when the office 365 apps use their 'modern auth' method for authentication. If I authenticate through an ECP request there is no error. I'll have my network team take a look at the LB configuration.

Thanks all!





On Mon, Jun 26, 2017 at 5:07 PM -0700, "Klingenstein, Nate [via Shibboleth]" <ml+s1660669n7634080h58 at n2.nabble.com<mailto:ml+s1660669n7634080h58 at n2.nabble.com>> wrote:

> It is about as far from abstract as it's possible to get.

I'll rephrase.  "The routing is too complicated for me to understand."
--
To unsubscribe from this list send an email to [hidden email]</user/SendEmail.jtp?type=node&node=7634080&i=0>


________________________________
If you reply to this email, your message will be added to the discussion below:
http://shibboleth.1660669.n2.nabble.com/NoSuchFlowExecutionException-with-office365-apps-tp7634076p7634080.html
To unsubscribe from NoSuchFlowExecutionException with office365 apps, click here<http://shibboleth.1660669.n2.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=7634076&code=cGVkcm8ucml2YXM2NjRAY3N1Y2kuZWR1fDc2MzQwNzZ8LTEyMzQ0MjQ2MDQ=>.
NAML<http://shibboleth.1660669.n2.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>




--
View this message in context: http://shibboleth.1660669.n2.nabble.com/NoSuchFlowExecutionException-with-office365-apps-tp7634076p7634086.html
Sent from the Shibboleth - Users mailing list archive at Nabble.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20170626/a263049e/attachment.html>