Known Issues

We are working hard to make Stadium even better with each new release. To prioritize our efforts and help our users to optimally use Stadium it is important to identify important limitations and issues.


List of Issues


Authentication

Single Sign-on: OIDC now uses PKCE

Since the Stadium 6 release, applications can't continue using the implicit flow with a Client Secret anymore because the client secret would be exposed in the browser. Therefore, Stadium 6 had to change over to the Authorization Code flow (using PKCE).

Impact

This is a breaking change in applications using Single Sign-on as authentication, and which were deployed before the Stadium 6 release.

Any application that was setup in Auth0, Okta or AzureAD has to be changed in the OIDC provider itself to use the Authorization Code flow.

Action

For Auth0 and AzureAD update the config settings. For Okta, recreate your Okta application.



Controls

Date Picker

Since the Stadium 6 release, custom date formats using the characters ~ \ _ don't work with the DatePicker control.

Impact

Applications that use any of the characters ~ \ _ in date formats will not return the date in the expected format.

Action

Update date formats to not use the characters ~ \ _ .



Actions

NavigateToPage

Since the Stadium 6 release, using NavigateToPage as a means to reset the controls on the current page will not work anymore.

Impact

Controls will not be reset in applications where NavigateToPage is used to reset the controls on the current page.

Action

Update applications to avoid using NavigateToPage to reset the controls on the current page.



Features

Embedded Files

Since the Stadium 6 release, Embedded file names no longer allow the characters ! # % + .

Impact

Applications that use any of the characters ! # % + in embedded file names will receive a validation error.

Action

Update embedded file names to not use the characters ! # % + .

Session Variables

Since the Stadium 6 release, uninitialized Session Variables are now not initialized to null but undefined.

Impact

It will cause an issue when an uninitialized session variable's value is concatenated with another variable's value.

Action

Ensure all session variables are initialized, especially when the session variable's value is used somewhere in your application in concatenation with other values.