You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 14, 2020. It is now read-only.
The process of upgrading from old version of Gluu Server to new version of Gluu Server generally require some changes to the data layer. So simply switching the containers from 3.1.2 to 3.1.3 isn't a painless process as sometimes new schema is necessary, or additional attributes are added to certain types of entries.
These examples can all be seen here. For 3.1.* it's mostly schema changes, since changing oxTrust or oxAuth from 3.1.2 to 3.1.3 will handle the war file upgrades.
Going forward, we have to have a process by which customers can relatively easily upgrade the data layer to work with newer versions in the future.
The text was updated successfully, but these errors were encountered:
Here is an upgrade script that will automatically upgrade Gluu Server in place. We should take this as an example for upgrading the LDAP data for 3.1.4, as that's the only persistence layer that would impact version swaps.
The process of upgrading from old version of Gluu Server to new version of Gluu Server generally require some changes to the data layer. So simply switching the containers from 3.1.2 to 3.1.3 isn't a painless process as sometimes new schema is necessary, or additional attributes are added to certain types of entries.
These examples can all be seen here. For 3.1.* it's mostly schema changes, since changing oxTrust or oxAuth from 3.1.2 to 3.1.3 will handle the war file upgrades.
Going forward, we have to have a process by which customers can relatively easily upgrade the data layer to work with newer versions in the future.
The text was updated successfully, but these errors were encountered: