forked from emmartins/wildfly-server-migration
-
Notifications
You must be signed in to change notification settings - Fork 38
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #302 from emmartins/CMTOOL-356_CMTOOL-357
[CMTOOL-356] [CMTOOL-357] Document new/updated migration tasks
- Loading branch information
Showing
50 changed files
with
567 additions
and
108 deletions.
There are no files selected for viewing
22 changes: 22 additions & 0 deletions
22
...erMigration-ManagedDomain-DomainConfiguration-MigrateLegacySecurityDomains.adoc
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,22 @@ | ||
| = Migrate Legacy Security Domains | ||
|
|
||
| {server-target-productName} does not supports the legacy Security Domains framework, and the tool migrates any usage of such resources to instead use the default {server-target-productName} Elytron replacements. | ||
|
|
||
| Please note that further manual Elytron configuration may be needed if the legacy Security Domain(s) being used were not the {server-source-productName}'s defaults! | ||
| The console logs all configuration resources migrated to the default {server-target-productName} Elytron replacements, for each configuration profile. | ||
| [source,options="nowrap"] | ||
| ---- | ||
| WARN Migrated ejb3 subsystem resource /profile/default/subsystem/ejb3/application-security-domain/other using legacy security domain other, to Elytron's default application Security Domain. Please note that further manual Elytron configuration may be needed if the legacy security domain being used was not the source server's default Application Domain configuration! | ||
| WARN Migrated undertow subsystem resource /profile/default/subsystem/undertow/application-security-domain/other using legacy security domain other, to Elytron's default application Security Domain. Please note that further manual Elytron configuration may be needed if the legacy security domain being used was not the source server's default Application Domain configuration! | ||
| WARN Migrated ejb3 subsystem resource /profile/full/subsystem/ejb3/application-security-domain/other using legacy security domain other, to Elytron's default application Security Domain. Please note that further manual Elytron configuration may be needed if the legacy security domain being used was not the source server's default Application Domain configuration! | ||
| WARN Migrated undertow subsystem resource /profile/full/subsystem/undertow/application-security-domain/other using legacy security domain other, to Elytron's default application Security Domain. Please note that further manual Elytron configuration may be needed if the legacy security domain being used was not the source server's default Application Domain configuration! | ||
| WARN Migrated messaging-activemq subsystem server resource /profile/full/subsystem/messaging-activemq/server/default, to Elytron's default application Security Domain. Please note that further manual Elytron configuration may be needed if the legacy security domain being used was not the source server's default Application Domain configuration! | ||
| WARN Migrated iiop-openjdk subsystem resource using legacy security domain to Elytron defaults. Please note that further manual Elytron configuration should be needed! | ||
| WARN Migrated ejb3 subsystem resource /profile/ha/subsystem/ejb3/application-security-domain/other using legacy security domain other, to Elytron's default application Security Domain. Please note that further manual Elytron configuration may be needed if the legacy security domain being used was not the source server's default Application Domain configuration! | ||
| WARN Migrated undertow subsystem resource /profile/ha/subsystem/undertow/application-security-domain/other using legacy security domain other, to Elytron's default application Security Domain. Please note that further manual Elytron configuration may be needed if the legacy security domain being used was not the source server's default Application Domain configuration! | ||
| WARN Migrated ejb3 subsystem resource /profile/full-ha/subsystem/ejb3/application-security-domain/other using legacy security domain other, to Elytron's default application Security Domain. Please note that further manual Elytron configuration may be needed if the legacy security domain being used was not the source server's default Application Domain configuration! | ||
| WARN Migrated undertow subsystem resource /profile/full-ha/subsystem/undertow/application-security-domain/other using legacy security domain other, to Elytron's default application Security Domain. Please note that further manual Elytron configuration may be needed if the legacy security domain being used was not the source server's default Application Domain configuration! | ||
| WARN Migrated messaging-activemq subsystem server resource /profile/full-ha/subsystem/messaging-activemq/server/default, to Elytron's default application Security Domain. Please note that further manual Elytron configuration may be needed if the legacy security domain being used was not the source server's default Application Domain configuration! | ||
| WARN Migrated iiop-openjdk subsystem resource using legacy security domain to Elytron defaults. Please note that further manual Elytron configuration should be needed! | ||
| ---- |
27 changes: 27 additions & 0 deletions
27
...verMigration-ManagedDomain-DomainConfiguration-MigrateLegacySecurityRealms.adoc
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,27 @@ | ||
| = Migrate Legacy Security Realms | ||
|
|
||
| {server-target-productName} does not supports the legacy Security Realms framework, and the tool migrates any usage of such resources to instead use the default {server-target-productName} Elytron replacements. | ||
|
|
||
| Please note that further manual Elytron configuration may be needed if the legacy security realm(s) being used were not the {server-source-productName}'s defaults! | ||
| The console logs all configuration resources migrated to the default {server-target-productName} Elytron replacements, for each configuration profile. | ||
| [source,options="nowrap"] | ||
| ---- | ||
| INFO Legacy security XML configuration retrieved. | ||
| WARN Migrated Remoting subsystem's http connector resource /profile/full-ha/subsystem/remoting/http-connector/http-remoting-connector using a legacy security-realm, to Elytron's default application SASL Authentication Factory migration-defaultApplicationSaslAuthenticationFactory. Please note that further manual Elytron configuration may be needed if the legacy security realm being used was not the source server's default Application Realm configuration! | ||
| WARN Migrated Undertow subsystem https-listener resource /profile/full-ha/subsystem/undertow/server/default-server/https-listener/https using a legacy security-realm, to Elytron's default TLS ServerSSLContext migration-defaultTLSServerSSLContext. Please note that further manual Elytron configuration may be needed if the legacy security realm being used was not the source server's default Application Realm configuration! | ||
| WARN Migrated Undertow subsystem http-invoker resource /profile/full-ha/subsystem/undertow/server/default-server/host/default-host/setting/http-invoker using a legacy security-realm, to Elytron's default Application HTTP AuthenticationFactory migration-defaultApplicationHttpAuthenticationFactory. Please note that further manual Elytron configuration may be needed if the legacy security realm being used was not the source server's default Application Realm configuration! | ||
| INFO Legacy security realms migrated to Elytron. | ||
| WARN Migrated Remoting subsystem's http connector resource /profile/full/subsystem/remoting/http-connector/http-remoting-connector using a legacy security-realm, to Elytron's default application SASL Authentication Factory migration-defaultApplicationSaslAuthenticationFactory. Please note that further manual Elytron configuration may be needed if the legacy security realm being used was not the source server's default Application Realm configuration! | ||
| WARN Migrated Undertow subsystem https-listener resource /profile/full/subsystem/undertow/server/default-server/https-listener/https using a legacy security-realm, to Elytron's default TLS ServerSSLContext migration-defaultTLSServerSSLContext. Please note that further manual Elytron configuration may be needed if the legacy security realm being used was not the source server's default Application Realm configuration! | ||
| WARN Migrated Undertow subsystem http-invoker resource /profile/full/subsystem/undertow/server/default-server/host/default-host/setting/http-invoker using a legacy security-realm, to Elytron's default Application HTTP AuthenticationFactory migration-defaultApplicationHttpAuthenticationFactory. Please note that further manual Elytron configuration may be needed if the legacy security realm being used was not the source server's default Application Realm configuration! | ||
| INFO Legacy security realms migrated to Elytron. | ||
| WARN Migrated Remoting subsystem's http connector resource /profile/ha/subsystem/remoting/http-connector/http-remoting-connector using a legacy security-realm, to Elytron's default application SASL Authentication Factory migration-defaultApplicationSaslAuthenticationFactory. Please note that further manual Elytron configuration may be needed if the legacy security realm being used was not the source server's default Application Realm configuration! | ||
| WARN Migrated Undertow subsystem https-listener resource /profile/ha/subsystem/undertow/server/default-server/https-listener/https using a legacy security-realm, to Elytron's default TLS ServerSSLContext migration-defaultTLSServerSSLContext. Please note that further manual Elytron configuration may be needed if the legacy security realm being used was not the source server's default Application Realm configuration! | ||
| WARN Migrated Undertow subsystem http-invoker resource /profile/ha/subsystem/undertow/server/default-server/host/default-host/setting/http-invoker using a legacy security-realm, to Elytron's default Application HTTP AuthenticationFactory migration-defaultApplicationHttpAuthenticationFactory. Please note that further manual Elytron configuration may be needed if the legacy security realm being used was not the source server's default Application Realm configuration! | ||
| INFO Legacy security realms migrated to Elytron. | ||
| WARN Migrated Remoting subsystem's http connector resource /profile/default/subsystem/remoting/http-connector/http-remoting-connector using a legacy security-realm, to Elytron's default application SASL Authentication Factory migration-defaultApplicationSaslAuthenticationFactory. Please note that further manual Elytron configuration may be needed if the legacy security realm being used was not the source server's default Application Realm configuration! | ||
| WARN Migrated Undertow subsystem https-listener resource /profile/default/subsystem/undertow/server/default-server/https-listener/https using a legacy security-realm, to Elytron's default TLS ServerSSLContext migration-defaultTLSServerSSLContext. Please note that further manual Elytron configuration may be needed if the legacy security realm being used was not the source server's default Application Realm configuration! | ||
| WARN Migrated Undertow subsystem http-invoker resource /profile/default/subsystem/undertow/server/default-server/host/default-host/setting/http-invoker using a legacy security-realm, to Elytron's default Application HTTP AuthenticationFactory migration-defaultApplicationHttpAuthenticationFactory. Please note that further manual Elytron configuration may be needed if the legacy security realm being used was not the source server's default Application Realm configuration! | ||
| INFO Legacy security realms migrated to Elytron. | ||
| ---- |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
5 changes: 5 additions & 0 deletions
5
...7.0toEAP8.0-ServerMigration-ServerConfiguration-Subsystem-Migrate-keycloak.adoc
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,5 @@ | ||
| :subsystem-migrate-legacySubsystemName: keycloak | ||
| :subsystem-migrate-legacyExtensionName: org.keycloak.keycloak-adapter-subsystem | ||
| :subsystem-migrate-replacementSubsystemName: elytron-oidc-client | ||
|
|
||
| include::ServerMigration-ServerConfiguration-Subsystem-Migrate.adoc[] |
5 changes: 5 additions & 0 deletions
5
...0toEAP8.0-ServerMigration-ServerConfiguration-Subsystem-Migrate-picketlink.adoc
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,5 @@ | ||
| :subsystem-migrate-legacySubsystemName: picketlink-federation | ||
| :subsystem-migrate-legacyExtensionName: org.wildfly.extension.picketlink | ||
| :subsystem-migrate-replacementSubsystemName: keycloak-saml | ||
|
|
||
| include::ServerMigration-ServerConfiguration-Subsystem-Migrate.adoc[] |
15 changes: 6 additions & 9 deletions
15
...AP7.0toEAP8.0-ServerMigration-ServerConfiguration-Subsystem-Update-jgroups.adoc
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,14 +1,11 @@ | ||
| = Update the JGroups Subsystem | ||
| = Update jgroups Subsystem Configuration | ||
|
|
||
| The JBoss Server Migration Tool does the following updates to any *jgroups* subsystem configuration found while migrating a server configuration: | ||
| The JBoss Server Migration Tool currently is not capable to automate the migration of the `jgroups` subsystem configuration, and thus reverts it to the default {server-target-productName} `jgroups` configuration. | ||
|
|
||
| * Replaces protocol `FRAG2` with `FRAG3`. | ||
| If you prefer, you can set the `subsystem.jgroups.update.skip` environment property to `true` to skip automatic update of the *jgroups* subsystem configuration. | ||
|
|
||
| Upon successful migration of the *jgroups* subsystem configuration, you should see the following message in the console: | ||
| Please note that further manual `jgroups` subsystem configuration may be needed if the configuration being used was not the default {server-source-productName} `jgroups` subsystem configuration! | ||
|
|
||
| The console logs a message when it updates the `jgroups` subsystem configuration. | ||
| [source,options="nowrap"] | ||
| ---- | ||
| INFO Subsystem jgroups updated. | ||
| ---- | ||
| WARN Configuration of JGroups protocols has been changed to match the default protocols of the target server. Please note that further manual configuration may be needed if the legacy configuration being used was not the source server's default configuration! | ||
| ---- |
12 changes: 12 additions & 0 deletions
12
...tandaloneServer-StandaloneServerConfiguration-MigrateLegacySecurityDomains.adoc
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,12 @@ | ||
| = Migrate Legacy Security Domains | ||
|
|
||
| {server-target-productName} does not supports the legacy Security Domains framework, and the tool migrates any usage of such resources to instead use the default {server-target-productName} Elytron replacements. | ||
|
|
||
| Please note that further manual Elytron configuration may be needed if the legacy Security Domain(s) being used were not the {server-source-productName}'s defaults! | ||
| The console logs all configuration resources migrated to the default {server-target-productName} Elytron replacements. | ||
| [source,options="nowrap"] | ||
| ---- | ||
| WARN Migrated ejb3 subsystem resource /subsystem/ejb3/application-security-domain/other using legacy security domain other, to Elytron's default application Security Domain. Please note that further manual Elytron configuration may be needed if the legacy security domain being used was not the source server's default Application Domain configuration! | ||
| WARN Migrated undertow subsystem resource /subsystem/undertow/application-security-domain/other using legacy security domain other, to Elytron's default application Security Domain. Please note that further manual Elytron configuration may be needed if the legacy security domain being used was not the source server's default Application Domain configuration! | ||
| ---- |
15 changes: 15 additions & 0 deletions
15
...StandaloneServer-StandaloneServerConfiguration-MigrateLegacySecurityRealms.adoc
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,15 @@ | ||
| = Migrate Legacy Security Realms | ||
|
|
||
| {server-target-productName} does not supports the legacy Security Realms framework, and the tool migrates any usage of such resources to instead use the default {server-target-productName} Elytron replacements. | ||
|
|
||
| Please note that further manual Elytron configuration may be needed if the legacy security realm(s) being used were not the {server-source-productName}'s defaults! | ||
| The console logs all configuration resources migrated to the default {server-target-productName} Elytron replacements. | ||
| [source,options="nowrap"] | ||
| ---- | ||
| INFO Legacy security XML configuration retrieved. | ||
| WARN Migrated Remoting subsystem's http connector resource /subsystem/remoting/http-connector/http-remoting-connector using a legacy security-realm, to Elytron's default application SASL Authentication Factory migration-defaultApplicationSaslAuthenticationFactory. Please note that further manual Elytron configuration may be needed if the legacy security realm being used was not the source server's default Application Realm configuration! | ||
| WARN Migrated Undertow subsystem https-listener resource /subsystem/undertow/server/default-server/https-listener/https using a legacy security-realm, to Elytron's default TLS ServerSSLContext migration-defaultTLSServerSSLContext. Please note that further manual Elytron configuration may be needed if the legacy security realm being used was not the source server's default Application Realm configuration! | ||
| WARN Migrated Undertow subsystem http-invoker resource /subsystem/undertow/server/default-server/host/default-host/setting/http-invoker using a legacy security-realm, to Elytron's default Application HTTP AuthenticationFactory migration-defaultApplicationHttpAuthenticationFactory. Please note that further manual Elytron configuration may be needed if the legacy security realm being used was not the source server's default Application Realm configuration! | ||
| INFO Legacy security realms migrated to Elytron. | ||
| ---- |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.