Releases: cmu-sei/Alloy.Ui
3.3.0-rc1
Full Changelog: 3.2.6...3.3.0-rc1
3.2.6
What's Changed
- fixed invite link in path-based routing environments by @sei-aschlackman in #596
- fixed redirect to support path-based routing by @sei-aschlackman in #607
Full Changelog: 3.2.4...3.2.6
Contributors
Assets 2
3.2.5
What's Changed
- fix duration hours form control by @sei-aschlackman in #397
Full Changelog: 3.2.3...3.2.5
Contributors
Assets 2
3.2.4
Fix Details
Alloy UI nginx default.conf was causing a redirect to port 8080 when the URI, did not have / at the end.
3.2.3
Enhancement Details
- bugfix: fixed Dockerfile and basehref script
- Dockerfile was not implementing entry scripts
- html file permissions changed to nginx due to unprivileged nginx
- basehref script had the wrong directory
- Removed double dot (../) and absolute paths
- Paths were breaking applications that utilize basehref
- Updated Dockerfile
- Removed ebram from code owners
3.2.2
3.2.1
Note: The release notes for 3.2.1, 3.2.0, and 3.1.0 are combined here.
Enhancement Details
Users can now invite other users to participate in an Event by creating an Invite link; any valid user can access the Event using the invite link.
Paging and other performance enhancements were added to the Event Templates section in Alloy.
Users can now be invited to unpublished Events.
Fix Details
Several issues in Event Details, including showing the status for the wrong event, missing timer for invited users, and showing end/invite buttons for invited users have been fixed.
Several issues with date/time handling in Alloy have been fixed, including:
- API now correctly returns UTC date/time
- Time Remaining displays correctly
- Countdown for Time Remaining implemented; page refresh to see updated time remaining no longer needed
- User is again redirected to homepage when an Event has ended
3.0.1
3.0.0
There are no fix details or known issues to report in version 3.0.0.
Enhancement Details
Breaking Change!
In the Identity server, the use of implicit flow is no longer recommended for OAuth 2.0 clients. The current recommendation is to use authorization code flow and PKCE. This change makes the default deployment authorization code.
System administrators must adjust the IdentityServer client for this application to use Authorization Code flow with PKCE instead of the implicit flow.
Administrators will need to change the appsettings entry OIDCSettings.response_type from id_token token to code.
Note: If this breaking change is not made, then Alloy.Ui can't properly authenticate with IdentityServer.