Tuesday, May 9, 2017
Tuesday, January 24, 2017
Thursday, January 5, 2017
Could not connect to SMTP host: smtp.gmail.com, port: 465
Status Description
javax.mail.MessagingException: Could not connect to SMTP host: smtp.gmail.com, port: 465; nested exception is: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
openssl s_client -connect smtp.gmail.com:465 > gmail-smtp-cert.pem
keytool -import -alias smtp.gmail.com -keystore /us1001/fmw/12c/wlserver/server/lib/DemoTrust.jks -file /us1001/fmw/12c/user_projects/domains/poc_domain/cert/gmail-smtp-cert.pem
If any issue please delete and re import the same
/usr/java/latest/jre/bin/./keytool -delete -alias smtp.gmail.com -keystore /us1001/fmw/12c/wlserver/server/lib/DemoTrust.jks -file /us1001/fmw/12c/user_projects/domains/poc_domain/cert/gmail-smtp-cert.pem
Sunday, July 10, 2016
Regenerate the DemoIdentity.jks and DemoTrust.jks keystores
Regenerate the DemoIdentity.jks and DemoTrust.jks keystores
By default, WebLogic Server is configured with two keystores:
• DemoIdentity.jks—Contains a demonstration private key for WebLogic Server. This keystore contains the identity for WebLogic Server.
• DemoTrust.jks—Contains the trusted certificate authorities from the WL_HOME\server\lib\DemoTrust.jks and the JDK cacerts keystores. This keystore establishes trust for WebLogic Server.
These keystores are located in the WL_HOME\server\lib directory.
NOTE: We do not use the demonstration keystores in a production environment.
Let’s See how we can regenerate the DemoIdentity.jks and DemoTrust.jks keystores.
By default, WebLogic Server is configured with two keystores:
• DemoIdentity.jks—Contains a demonstration private key for WebLogic Server. This keystore contains the identity for WebLogic Server.
• DemoTrust.jks—Contains the trusted certificate authorities from the WL_HOME\server\lib\DemoTrust.jks and the JDK cacerts keystores. This keystore establishes trust for WebLogic Server.
These keystores are located in the WL_HOME\server\lib directory.
NOTE: We do not use the demonstration keystores in a production environment.
Let’s See how we can regenerate the DemoIdentity.jks and DemoTrust.jks keystores.
1.Re-generating DemoIdentity.jks
Set Class Path by running below
. <WL_HOME>/server/bin/setWLSEnv.sh (Unix) (use the 'dot' to run the script in the same shell)
• Execute this command to generate identity entities (certificate plus key):
java utils.CertGen -keyfilepass DemoIdentityPassPhrase -certfile democert -keyfile demokey -strength 1024
NOTE: This would create the files in the present working directory.
• Execute this command to import the identiy entities into Java Keystore:
java utils.ImportPrivateKey -keystore DemoIdentity.jks -storepass DemoIdentityKeyStorePassPhrase -keyfile demokey.pem -keyfilepass DemoIdentityPassPhrase -certfile democert.pem -alias demoidentity
NOTE: This would create "DemoIdentity.jks" in the present working directory.
• Confirm that the certificate (along with key) is imported:
keytool -list -v -keystore DemoIdentity.jks
2.Re-generating DemoTrust.jks
Set Class Path by sourcing setWLSEnv.sh
. <WL_HOME>/server/bin/setWLSEnv.sh (Unix) (use the 'dot' to run the script in the same shell)
• Execute below command to import the Demo CA into DemoTrust.jks:
keytool -importcert -trustcacerts -alias wlscertgencab -keystore DemoTrust.jks -storepass DemoTrustKeyStorePassPhrase -file <WL_HOME>\server\lib\CertGenCA.der
NOTE: This would create "DemoTrust.jks" in the present working directory if there is no file named "DemoTrust.jks" present there. However, if there is any such keystore file already present in the present directory, then it would simply import the certificate as a trusted entry into this keystore file. A path can also be prefixed to the keystore name in the command argument "-keystore" above such that the keystore is created at the specified location instead of in present working directory.
Tuesday, February 16, 2016
Exception Description: Cannot acquire data source [jdbc/BeamNonJTADataSource].
Internal Exception: javax.naming.NameNotFoundException: Unable to resolve 'jdbc.BeamNonJTADataSource'. Resolved 'jdbc'; remaining name 'BeamNonJTADataSource'
After Applying below patches we see that error in BAM Log files and BAM wont come up.
Another issue is in admin console bam status will show starting.
Patch 21885138 (BP4),22524811(BP5)
Patch 22144497 : MERGE REQUEST ON TOP OF SOA BP 12.1.3.0.4 FOR BUGS 21438873 21488819 21883560
Patch 22144471 : MERGE REQUEST ON TOP OF SOA BP 12.1.3.0.4 FOR BUGS 19154446 21466129
Patch 22190179 : MERGE REQUEST ON TOP OF SOA BP 12.1.3.0.4 FOR BUGS 22144523 22127760
Patch 22237005 : MERGE REQUEST ON TOP OF SOA BP 12.1.3.0.4 FOR BUGS 21238852 21418640
Patch 20484519 - BAM 12c Performance / Scalability
Patch 20835861 - EMS : Status shown in the UI is not correct
Patch 20744648 - Collapsed List header alignment not aligning to Left fully.
Patch 22013059 - Add DataObject Metadata Caching to Improve Performance
Please
do the following to start BAM Server.
1. Create a new Generic Data Source called BamNonJTADataSource using the JNDI Name jdbc/BeamNonJTADataSource.
2. Specify Oracle's Driver (Thin) for Instance connections; Version:Any as the Database Driver.
3. Make sure the Supports Global Transactions checkbox is unchecked.
4. Copy the Database Name, Host Name, Port, Database User Name and Password from the existing BamDataSource Data Source.
5. Target the new Data Source to all servers in the BAM cluster or to the single BAM Server if not in a clustered environment.
Refer to this document for detailed instructions:
http://www.oracle.com/technetwork/middleware/bam/community/instruct-patch-20484519-2479103.pdf
Thursday, September 10, 2015
Recover WebLogic Server Admin Password
Recover WebLogic Server Admin Password
1. Please save below script as recoveradminpass.py for real time best practice save this file in shared drive which can be access from all servers.
from weblogic.security.internal import *
from weblogic.security.internal.encryption import *
encryptionService = SerializedSystemIni.getEncryptionService(".")
clearOrEncryptService = ClearOrEncryptedService(encryptionService)
# Take encrypt password from user
pwd = raw_input("Paste encrypted password ({AES}fk9EK...): ")
# Delete unnecessary escape characters
preppwd = pwd.replace("\\", "")
# Display password
print "Decrypted string is: " + clearOrEncryptService.decrypt(preppwd)
2. Set domain environment variables
source $DOMAIN_HOME/bin/setDomainEnv.sh
3. Get encrypted password from boot.properties file of AdminServer
#Password:
grep password $DOMAIN_HOME/servers/AdminServer/security/boot.properties | sed -e "s/^password=\(.*\)/\1/"
4. Navigate to $DOMAIN_HOME/security directory and run the following command to start decryption:
cd $DOMAIN_HOME/security
java weblogic.WLST location/recoveradminpass.py
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
Paste encrypted password ({AES}fk9EK...): {AES}dXHAlPujdpMNKUNDUJuGtcZiWmLagbtNFexVPAi4sek=
Decrypted string is: welcome123
Tuesday, July 21, 2015
SSL Notes
Understanding SSL communication
What is SSL?
SSL stands for Secure Sockets Layer. It is a technology using which the data exchange between two systems are encrypted so that no one except the systems involved can interpret the data.
As you can see in the picture above, SSL communication involves a client and a server. Client is most probably a browser from a user’s PC, even though it can be a server application communicating with another server application. The server is most probably a Web Server, even though it can be any ssl enabled server application such as a Database Server or a Message queueing Server.
When you access a website using your browser, if the site is SSL enabled, you can see the security information in the browser. For example, see image below.
Note that SSL is a protocol, meaning various software products and frameworks implement SSL a little differently. However they must all adhere to the SSL specification. From Administration and Support perspective, what this means is you will have to do a bit of a reading to support SSL with various products. For example, while it is true that you need to add the CA certificate of the remote system you are trying to connect to your trust store, the steps you must follow for a WebLogic Application server will be different from a Jboss Application Server. I will explain all about CA certs in a sec
TLS, which stands for Transport Layer Security is the new generation SSL (After SSL version 3.0, it is TLS). As you can guess, TLS is the preferred protocol as it is newer (TLS 1.2 is the latest as of June 2015).
In the OSI Network model, SSL/TLS will fit in somewhere between Transport and Application layer.
SSL provides for two key security aspects in a client-server communication.
Authentication: You are guaranteed to communicate with the system that you are trying to communicate with (unless you are victim of Man in the Middle attack)
Encryption: The data being exchanged is guaranteed to be decrypted ONLY by you and the system you are communicating with (unless someone gets access to your private key)
How does SSL work?
SSL is based on Public Key Cryptography. Let us take a simple case to illustrate how it works.
A Web Server that wants to use SSL for its communication with the clients will first obtain a Private Key and a corresponding Public key (this is called Key Pair as they are mathematically related). When a client accesses the Web Server (for example, using the URL https://yourserver.com), the server sends the public key to the client. The client encrypts the data using the public key (or a derivative of the public key) which can be decrypted ONLY by someone who has the private key; in this case it is your server.
Public keys come in various strengths, depending on their size. A strong key size is 2048 bits. A 2048 bits RSA Public key looks like below:
30 82
Public keys come in various strengths, depending on their size. A strong key size is 2048 bits. A 2048 bits RSA Public key looks like below:
30 82 01 0a 02 82 01 01 00 b9 4b 64 43 5c 68 dc 87 6b 29 6f 5d 2b 2d 50 80 e1 38 1e 07 f4 e2 34 b1 cf 73 37 8a 30 9c c8 63 da 8a 50 64 1f 71 80 93 c1 f5 9e d8 4d 71 05 ea ff 8b 43 97 21 47 1a fb f0 6b dc 74 ca da a9 0d a1 cf e7 b8 59 09 27 77 a3 d7 b0 3d 2a fd 44 62 1b
Note: Larger keys come with some performance hit but it is more difficult to crack. You must use at least 2048 bits.
Where do SSL certificates come into play?
A SSL certificate is nothing but a file containing Signed Public Key. It is a secure mechanism to send the Public key. More importantly, since the public key is signed, it proves the validity of the certificate (Authentication).
Here is how it works:
When a Server wants to enable SSL, it generates a key pair (the method of creating the key pair depends on the technology/product it is using. But typically java based applications can use the application ‘keytool’ that comes with Java). It then applies for a singed public key. It does so by creating a CSR (Certificate signing request) and sending it to a CA (Certificate authority). Upon reviewing the application, CA generates a Certificate chain which includes the Server certificate (signed public key) and a certificate (or certificates) of the CA itself. This certificate chain will need to be installed in the Server application (again, installing the server certificate depends on the product/technology the server is using).
To summarize:
1. Server generates a private key and a public key
2. Server generates and submits a CSR (Certificate signing request) to a CA (Certificate authority such as Symantec)
3. CA generates a Certificate chain containing the Server certificate (signed public key) and a certificate (or certificates) of the CA itself.
4. This certificate chain will need to be installed in the Server application
Taking a deeper look at a SSL certificate
Will keep update this ....
Thursday, July 2, 2015
Oracle Critical Patch Updates for Weblogic/SOA
http://www.oracle.com/technetwork/topics/security/cpujul2014-1972956.html
http://www.oracle.com/technetwork/topics/security/cpuoct2014-1972960.html
http://www.oracle.com/technetwork/topics/security/cpujan2015-1972971.html
http://www.oracle.com/technetwork/topics/security/cpuapr2015-2365600.html
|
Product Home |
Patch |
Advisory Number |
Comments |
|
WebLogic Server
10.3.6.0.0 home |
PSU 10.3.6.0.11 Patch 20181997 |
CVE-2014-3566, CVE-2015-0449 |
10.3.6
Patch Set Updates
|
PSU
|
Description
|
Patch Download
|
Patch Availability
Document
|
Smart Update Patch ID
|
Bugs fixed in this PSU
|
|
10..3.6.0.11
|
10.3.6.0.11
Patch Set Update (PSU) for WebLogic Server 10.3.6.0
|
YUIS
|
|||
|
10..3.6.0.10
|
10.3.6.0.10
Patch Set Update (PSU) for WebLogic Server 10.3.6.0
|
12UV
|
My Oracle Support Note 19637463.1
|
||
|
10.3.6.0.9
|
10.3.6.0.9
Patch Set Update (PSU) for WebLogic Server 10.3.6.0
|
FSR2
|
|||
|
10.3.6.0.8
|
10.3.6.0.8
Patch Set Update (PSU) for WebLogic Server 10.3.6.0
|
T5F1
|
Oracle
SOA Suite 11.1.1.7.0
https://support.oracle.com/epmos/faces/PatchDetail?_adf.ctrl-state=19l298hkuy_642&patch_name=20423535&releaseId=17111170&patchId=20423535&languageId=0&platformId=2000&_afrLoop=455304959776028
20423535 --SOA Bundle Patch 11.1.1.7.7 (Patch)
OSB: 11.1.1.7.0
20423630
- OSB Bundle
Patch 11.1.1.7.4 (Patch) 39.4 MB
Thursday, June 25, 2015
DataBase Connectivity Check form application server(weblogic/soa)
DataBase Connectivity Check form application server(weblogic/soa)
Command :java utils.dbping DBMS user password DB
Before executing below command u have to set envronment
cd $DOMAIN_HOME/bin
source setDomainEnv.sh
or cd $WL_HOME/server/bin
source setWLSEnv.sh
java utils.dbping ORACLE_THIN username password hostname:port/instance_name
Thursday, April 9, 2015
SOA/OSB 12C upgrade from 11.1.1.7
High Level Steps
Steps: High Level Steps
1. Prerequisites Check for Upgrade
2. Prepare
Install/Upgrade doc with new directory structure & ports(if req).
3. Backup Current System (APP+DB)
4. Install
new software under new location
5. Upgrade
Dehydration store (Schema Upgrade)
6. Upgrade
Domain
7. Reconfigure
Domain
8. Post Upgrade Activities
Subscribe to:
Posts (Atom)

