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
- If your SSH private key has a passphrase, watch the build closely because it will prompt for your passphrase multiple times.
55
58
Failure to enter it in a timely manner may result in a failure.
56
59
57
-
3. If the build fails, run the `mvn -B release:rollback` command to undo it and start over from Step 2., after correcting the issue.
58
-
4. After the software has been released, move on to the GitHub Release Process.
60
+
4. If the build fails, run the `mvn -B release:rollback` command to undo it and start over from Step 2., after correcting the issue.
61
+
5. After the software has been released, move on to the GitHub Release Process.
59
62
60
63
### GitHub release process
61
64
Note that this process relies on the WDT installers being in your local Maven repository. As such, it is critical for
62
65
the same user to run these steps on the same machine as the steps from the previous section!
63
66
64
-
1. Save the release notes in the file `<wdt-project-directory>/target/ReleaseNotes.md`.
65
-
2. Run the command `mvn -f github-release.xml -DreleaseVersion=<release version number> verify` to create the draft GitHub Release.
66
-
3. Log into [GitHub](https://github.com/oracle/weblogic-deploy-tooling), go to the Releases page, review/edit the draft release, and then publish the release.
67
+
1. Prior to starting the GitHub release, you *must* wait until all Jenkins activity triggered by the release is complete.
68
+
2. Save the release notes in the file `<wdt-project-directory>/target/ReleaseNotes.md`.
69
+
3. Run the command `mvn -f github-release.xml -DreleaseVersion=<release version number> verify` to create the draft GitHub Release.
70
+
4. Log into [GitHub](https://github.com/oracle/weblogic-deploy-tooling), go to the Releases page, review/edit the draft release, and then publish the release.
-#1682 - Added support for discovering built-in security provider data in online mode. This includes
21
+
DefaultAuthenticator users and groups, XACMLAuthorizer policies, XACMLRoleMapper roles, and DefaultCredentialMapper
22
+
user/password credential mappings. As with other discovery features, default values are filtered out and will not
23
+
appear in the model. By default, discovering users and credential mappings require the use of WDT encryption so that
24
+
no clear text passwords are stored in the model or variable files.
25
+
-#1682 - Normalized XACMLRoleMapper role handling by removing the previous discovery of XACMLRoleMapper roles (that was
26
+
not working with newer versions of WebLogic anyway) and removing version limitations during provisioning.
27
+
-#1682 - Deprecated the `-use_encryption` command-line argument and replaced it with `-passphrase_prompt` to make the
28
+
purpose of the argument clearer.
29
+
-#1682 - Relaxed the JDK 8 requirement to use WDT encryption. Later versions of JDK 7 have the necessary algorithm
30
+
support so now WDT determines at startup whether the underlying JDK supports WDT encryption or not.
31
+
-#1682 - Used the values of the `-admin_user` and provided password to populate the `domainInfo:/AdminUserName` and
32
+
`domainInfo:/AdminPassword` fields when discovering security provider data.
33
+
-#1688 - Enhanced variable tokenization support to include passwords in discovered security provider data.
34
+
-#1689 - Added the ability to discover the OPSS wallet when running in online mode.
35
+
-#1693 - Changed the `wko`, `wko-dii` (deprecated), and `wko-pv` target values to refer to the latest versions instead
36
+
of WebLogic Kubernetes Operator 3 versions. Added `wko3`, `wko3-dii`, and `wko3-pv` to accommodate users that still
37
+
require the ability to use these older versions.
38
+
-#1697 - Added support for the Prepare Model Tool to preserve any one-way hashed passwords in the model.
39
+
-#1700 - Added support for storing XACML policy and role definitions that could not be converted to their original
40
+
policy and role expressions as XACML files in the archive file.
41
+
42
+
#### Bug Fixes
43
+
-#1687 - Fixed a problem with the Discover Domain Tool not properly handling Data Source user names with spaces with
44
+
older versions of WebLogic Server.
45
+
-#1690 - Fixed a problem with determining the default security realm name that caused it to always be `myrealm`.
46
+
-#1692 - Fixed a misleading error message when the model points to an application outside of the archive file that
47
+
does not exist.
48
+
-#1695 - Fixed an issue where the WebLogic Kubernetes Operator `domain.yaml` was including a placeholder for the
49
+
`domainHome` attribute in all cases so that the WebLogic Image Tool could populate it when creating the image.
50
+
This was occurring even in use cases where the WebLogic Image Tool did not have this information. WDT no longer does
51
+
this and will only include the `domainHome` in the case where the user has specified it on the command line,
52
+
or in the `kubernetes` section of the model.
53
+
-#1698 - Fixed issues with the new messages related to the security provider data discovery features.
54
+
-#1701 - Moved the TestSummaryHandler logging class out of the installer since it is only meant for supporting unit tests.
55
+
-#1702 - Fixed a bug in deployment plan discovery for exploded applications.
56
+
-#1703 - Fixed a bug in discovery of `domainBin` scripts.
57
+
-#1705 - Added missing validation for the `WLSUserPasswordCredentialMappings` section.
58
+
-#1706 - Fixed a validation bug that was causing lax validation to fail when archive entries were missing.
59
+
-#1707 - Fixed a bug in the handling of the `ActiveContextHandlerEntry` attribute of an `Auditor` security provider.
60
+
61
+
#### Known Issues
62
+
- SSH support requires a reasonably recent version of Bouncy Castle. WDT picks up Bouncy Castle from WLST so, for example,
63
+
the 12.2.1.4.0 GA release fails with the following error, as mentioned at https://github.com/hierynomus/sshj/issues/895.
64
+
Applying a recent PSU should resolve the issue for 12.2.1.4 and 14.1.1.
65
+
66
+
```shell
67
+
SEVERE Messages:
68
+
1. WLSDPLY-20008: verifySSH argument processing failed: Failed to initialize SSH context: Failed to SSH connect to host myhost.oracle.com: no such algorithm: X25519 for provider BC
69
+
```
70
+
71
+
- SSH support for the Update Domain Tool and Deploy Apps Tool does not work when using an archive file and the remote
72
+
WebLogic Server is running on Windows using the optional, Windows-provided, OpenSSH component. This is due to an
73
+
issue with the SSHJ library WDT is using. See https://github.com/hierynomus/sshj/issues/929 for more information.
74
+
75
+
See https://oracle.github.io/weblogic-deploy-tooling/userguide/limitations/limitations/ for the current set of known limitations.
0 commit comments