search

FusionAuth / fusionauth-issues

FusionAuth issue submission project
https://fusionauth.io
90 stars 12 forks source link

Samlv2 IdP Initiated Identity Provider has weird view details screen #1200

Closed mooreds closed 3 years ago

mooreds commented 3 years ago

Samlv2 IdP Initiated Identity Provider has weird view details screen

Description

If you view details of a Samlv2 IdP Initiated Identity Provider, you see a weird screen, see screenshot.

In particular, no ACS or other details are provided. Perhaps that is intentional?

Affects versions

1.27, fresh install, using default theme, with two tenants. (same behavior with one tenant though.)

Steps to reproduce

  1. Make sure your instance has a license key
  2. go to identity providers
  3. add a samlv2 idp initiated identity provider (you may need to add an RSA verification key if you don't have one)
  4. save it
  5. view it by clicking the magnifying glass

You see what is in the screenshot.

Expected behavior

I'd expect either an ACS and other associated metadata or no "samlv2 integration details" section at all.

Screenshots

Screen Shot 2021-05-05 at 4 53 56 PM

Platform

Firefox

Additional context

I see the following log message in the system logs:

fusionauth_1  | 2021-05-05 11:04:02.644 PM ERROR io.fusionauth.app.primeframework.error.ExceptionExceptionHandler - An unhandled exception was thrown
fusionauth_1  | org.primeframework.mvc.PrimeException: The message for the key [acs] is missing and there was no default set using the [default] attribute.
fusionauth_1  |     at org.primeframework.mvc.control.message.Message.addAdditionalAttributes(Message.java:93)
fusionauth_1  |     at org.primeframework.mvc.control.AbstractControl.renderStart(AbstractControl.java:115)
fusionauth_1  |     at org.primeframework.mvc.control.FreeMarkerControlProxy.execute(FreeMarkerControlProxy.java:61)
fusionauth_1  |     at freemarker.core.Environment.visit(Environment.java:451)
fusionauth_1  |     at freemarker.core.UnifiedCall.accept(UnifiedCall.java:102)
voidmain commented 3 years ago

This will be fixed in version 1.27.2.

robotdan commented 3 years ago

Do you mean 1.27.1 ?

voidmain commented 3 years ago

Oops. I thought you had already released a patch to fix a few bugs.

Yes, this will be in 1.27.1 then.