We are using WSO2 5.4.1 version and trying to setup IWA using Kerberos. We have done all the configurations as mentioned in the following post.
https://medium.com/#farasath/integrated-windows-authentication-with-kerberos-and-wso2-identity-server-ffcd8263a0f1
When we try to access the application we are getting following exception.
We have checked all the configurations multiple times but not able to figure out the root cause. Can someone help us to find out what could be missing in this setup? Are we missing any additional step?
We have also tried with WSO2 IS version 5.5.0 but still getting same error.
How can we enable additional logging to see what is going wrong with kerberos token decryption?
It was indeed a JDK issue. For some reason we were using Oracle jdk1.8.0_45 and we were facing this issue. We had upgraded the version to jdk1.8.0_162 and we were able to proceed but then we encounter another problem. After authentication we were not getting remote claims in the response from WSO2 IS. As per this post (stackoverflow.com/questions/49997900/…) we upgraded to latest patch of WSO2 IS 5.5.0 and now it is working.
We are able to authenticate user using IWA-Kerberose.
Related
I am trying to enable SSL in a Telerik Reporting CORS REST Service. It is a .Net Framework 4.7 REST Api. Here's the screenshot of the error reflected in the browser.
I think I have a similar situation explained here, however my certificate was already trusted and adding it to the Root didn't solve the problem. Any ideas? Thanks
My issue was related to IIS Express. Uninstalling it and installing it back fixed the problem. Thanks a lot to this post.
We've used Artifactory 5.2.0 until today and had SAML configured and working. I just upgraded and now it doesn't work anymore. I'm being redirected to
https://MY_URL/artifactory/webapp/saml/loginResponse
which is not found.
Unfortunately I couldn't find any information about this on the Artifactory site - can anyone help?
I do not have access to ADFS directory unfortunately - we have an external partner for those kinds of things. But they told me that they haven't changed anything in their configuration.
Login into Artifactory works, also with LDAP and the new version works fine - except that one thing.
Turns out an ADFS patch was the problem and the message Artifactory got wasn't correct so obviously the login didn't work anymore. Unfortunately I didn't really get an error message that would have led me on the right path.
We fixed the ADFS, got a new certificate and now it's working again!
So right now I'm trying to make a bunch of REST API calls to Salesforce from my WebSphere server, but every time I make a request, I get a "500 Server Error" error message in my logs. I then tried to run my API calls through RunScope to try and debug what was going wrong. As soon as I sent my API calls through RunScope to Salesforce, the 500 Error went away and everything worked. I instantly thought it was some kind of SSL Protocol issue since Salesforce apparently doesn't support SSL3.0. So I checked my WebSphere configuration and noticed that it supports both SSL and TLS protocols (I'm not 100% sure which protocol it's using though, if anyone knows of a way to test that, that would be helpful). Now I'm pretty stumped. I know it's not a certificate issue because i installed the needed certificates on my WebSphere server. Anyone else have any ideas why the API calls work through RunScope to Salesforce but not directly to Salesforce? Any help is appreciated.
I figured it out. My issue was that my WebSphere server was running TLS1.0 which isn't supported anymore by Salesforce. If you're running into the same issues as me, make sure your server is running TLS 1.1 or higher.
I am trying to work out Liferay Authentication using wso2 Identity Server, I am using liferay 6.2 and Wso2 IS 5.0.0, I am following above link https://docs.wso2.com/display/IS500/Integrating+WSO2+Identity+Server+with+Liferay Accordingly I have created portal-ext.properties file under liferay_home/tomcat/webapps/ROOT/WEB-INF/classes/portal-ext.properties. and added following properties in it:
auth.pipeline.pre=org.wso2.liferay.is.authenticator.WSO2ISAuthenticator
auth.pipeline.enable.liferay.check=false
but when I run liferay portal and try to log in I am getting java.lang.ClassNotFoundException: org.wso2.liferay.is.authenticator.WSO2ISAuthenticator It should be in org.wso2.liferay.xacml.connector.jar but i am not getting this jar any where I tried to find out this class in other jars but unable to find it, I also tries to google it but no success, Please help me out with this problem, Thanks
You can follow the instructions in http://blog.facilelogin.com/2012/10/integrating-wso2-identity-server-with.html. You can find the missing jars from https://svn.wso2.org/repos/wso2/people/prabath/liferay.
We've managed to get talend MDM UI working fine over SSL, but we've not managed to get the MDM studio talk to the MDM server over SSL. Has anyone managed this? I've not tried the data integration input steps yet over SSL either.
I tried the forums - no joy.
I suspect for some reason it's not possible - And the reason I suspect this is that when you add an MDM server in TOS it prompts for port, hostname, user and password. Nowhere does it prompt for protocol.
One assumes that the EE version must surely support this? But we have a very simple model and wont be using EE as it would be OTT.
Thanks!
Dan
So it turns out this is a bug/unimplemented feature, and has been pencilled in to be fixed in 5.3.0 with luck!
https://jira.talendforge.org/browse/TMDM-4912