Topic Started
| Topics |
|---|
Our java application runs on WebSphere 8.5.5 and IBM Java 1.8
When attempting to connect to OneSpan the TLS Cipher negotiation is resulting in dropping down to TLS 1 which OneSpan then rejects.
So in
|
I've a request for clarification on the proxy configuration options.
When should withHttps be used versus withHttp and what difference does it make?
|
Based on past investigation and a recent onespan posting it appears callbacks remain the only way to get email bounce back, and pin lockout notification.
|
In looking at the audit service for a package there appears to be events worthy of being in an audit log but do not appear to be.
For example: PIN authentication failures show up, but not that access
|
Replies Created
Reply to: Email bounce, PIN lockout status availabe for each Signer
Wednesday, April 24, 2019 at 09:10amThanks. This does help.
Reply to: proxy config clarification request
Wednesday, September 18, 2019 at 08:01amYes thank you.
Reply to: IBM Java and TLS
Friday, September 20, 2019 at 12:01pmThanks, definitely something to try.
Subscriptions
| Topics | Replies | Freshness | Views | Users |
|---|---|---|---|---|
Our java application runs on WebSphere 8.5.5 and IBM Java 1.8
When attempting to connect to OneSpan the TLS Cipher negotiation is resulting in dropping down to TLS 1 which OneSpan then rejects.
So in
|
2 | 2 years 8 months ago | 107 | 
|
I've a request for clarification on the proxy configuration options.
When should withHttps be used versus withHttp and what difference does it make?
|
2 | 2 years 8 months ago | 32 |
|
Based on past investigation and a recent onespan posting it appears callbacks remain the only way to get email bounce back, and pin lockout notification.
|
2 | 3 years ago | 21 |
|
In looking at the audit service for a package there appears to be events worthy of being in an audit log but do not appear to be.
For example: PIN authentication failures show up, but not that access
|
1 | 3 years 1 month ago | 22 |
|