secureauthcorp / saidp-sdk-java Goto Github PK

Need to support delivery of One Time Passcodes in native languages.
This will need to become an option to add Accept Language as a configurable parameter

Add support for 9.0 IDM feature support

Add exception handling in the SDK. This will allow users of the SDK to not be required to parse responses to identify errors in response.

Is the current group-id correct? The maven metadata currently looks like:

<dependency>
    <groupId>org.secureauth.sarestapi</groupId>
    <artifactId>saRestApi</artifactId>
    <version>1.0.1-SNAPSHOT</version>
</dependency>

Hello,

It appears that the dependencies that the library is using are out-of-date.

Can you please update them?

Thank you,
Roman

Add support for the use of a spring template versus the use of jersey 1.x

@rrowcliffe @thomasleplus @CharlieC3 @elordahl

We are using websphere 9 as app server running on JAVA8 , and have currenlty support to TLS1.0 , TLS1.1 and TSL 1.2.
Error:Already connected javax.ws.rs.ProcessingException: Already connected error on making API calls

Stack :
https://XXXX:443/secureauth1/api/v1/adaptauth
Error:Already connected
javax.ws.rs.ProcessingException: Already connected
at org.glassfish.jersey.client.ClientRuntime.invoke(ClientRuntime.java:236)
at org.glassfish.jersey.client.JerseyInvocation$1.call(JerseyInvocation.java:655)
at org.glassfish.jersey.client.JerseyInvocation$1.call(JerseyInvocation.java:652)
at org.glassfish.jersey.internal.Errors.process(Errors.java:315)
at org.glassfish.jersey.internal.Errors.process(Errors.java:297)
at org.glassfish.jersey.internal.Errors.process(Errors.java:228)
at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:422)
at org.glassfish.jersey.client.JerseyInvocation.invoke(JerseyInvocation.java:652)
at org.glassfish.jersey.client.JerseyInvocation$Builder.method(JerseyInvocation.java:412)
at org.glassfish.jersey.client.JerseyInvocation$Builder.post(JerseyInvocation.java:321)
at org.secureauth.sarestapi.resources.SAExecuter.executePostRequest(SAExecuter.java:406)
at org.secureauth.sarestapi.SAAccess.adaptiveAuthQuery(SAAccess.java:188)

Properties set when creating api connection :
ssl=true
selfSigned=false or selfSigned=true ( both have same issue)

We also added self-signed cert on websphere , dint make any difference .

NOTE : I can make https calls from my local machine without any issue with the following property settings and no certs in place:

ssl=true
selfSigned=true

PS . found this piece of code in SAExceuter.java

org.secureauth.sarestapi.resources.SAExecuter#createConnection
ctx = SSLContext.getInstance("TLS"); does it supposed to be TLSv1.0 /TLSv1.2 ?

after migrating from v1.0.1 to v1.0.3, every API call to the secureAuth instance (v9.2.0) SAExecuter returns back "Bad Request"

Note : The same request(s) works with v1.0.1 .
Note: All provided integration tests are failing with the same issue.

PFA

@sa-rrowcliffe
validateUserPin call always returns pin as invalid even providing right pin value

scenario:
step1: deliverAdHocOTPByPhone ==> (userid , phoneNumber) ==>
{
"status": "valid",
"message": "",
"user_id": "userid",
"otp": 495723
}

step 2: validateOTP (userid, 495723) ==>
{
"status": "invalid",
"message": "PIN is invalid."
}

Note : this is happening with v1.0.1 and later API versions