I am trying to figure out a way to integrate Rundeck with Keycloak for SSO. But I am not able to find any way of doing it.
Can anyone tell me that which protocol does Rundeck support for SSO and how it can be integrated with Keycloak ?
The SSO feature is exclusive to Rundeck Pro. You can start a Trial to test its features and you will be entitled to receive support from the Rundeck team, that could assist you. Furthermore you could be contacted by a sales representative in order to evaluate such integration.
Cheers!
Related
By using pingfederate, I am asked to implement an SSO authentication feature (SAML2.0 or OpenId type) in a local web application, my concern is that I am a beginner on the use of pingfederate. Everything I've done so far is to have installed the pingfederate application and also the project in question then I tried to follow the documentation on the pingIdentity platform but that didn't help me much. So I come to look for solutions on the approaches that I have to do if someone could help me or guide me.
I tried to configure the connections between an IdP and pingfederate(as SP) and also the connection between pingfederate( as IdP) and my SP app but nothing works, maybe the configuration I did is not correct
what i want to do is to successfully implement this SSO (SAML2.0) authentication feature in my web application using pingfederate and I implore your help for the configuration steps that I have to do
By using pingfederate, I am asked to implement an SSO authentication feature (SAML2.0 or OpenId type) in a local web application, my concern is that I am a beginner on the use of pingfederate.
Everything I've done so far is to have installed the pingfederate application and also the project in question then I tried to follow the documentation on the pingIdentity platform but that didn't help me much. So I come to look for solutions on the approaches that I have to do if someone could help me or guide me.
I tried to configure the connections between an IdP and pingfederate(as SP) and also the connection between pingfederate( as IdP) and my SP app but nothing works, maybe the configuration I did is not correct
what i want to do is to successfully implement this SSO (SAML2.0) authentication feature in my web application using pingfederate and I implore your help for the configuration steps that I have to do
My organization has decided to use Drools as a decision management framework. We are using the new UI business-central which is deployed as a WAR file in WildFly server for managing the rules and the assets related to the rules.
We have licensed Gsuite for our emails and other activities. We want to use Google login for the users of the business-central system instead of the username and password-based auth provided.
One way to do it is by using a Keycloak server which will provide us a way to manage users and authentication. But we do not want to maintain an extra server just for authentication.
Can someone please help me in achieving this authentication? Also, it would be helpful if I can know in advance the pitfalls of such a type of authentication approach.
Here are the version details for the drools system:
Java: openjdk version "1.8.0_242"
Drools: 7.33.0.Final
After doing a lot of trial and error and quite a bit of googling around. I have reached the conclusion that providing social login in business-central should be done via Keycloak if you are using Wildfly.
There are a lot of security-related features that you will get out of the box and you won't have to tweak around the drools code and later on finding out that you have missed a use case.
I followed official documentation from : https://docs.wso2.com/display/IS541/Integrating+WSO2+Identity+Server+with+Liferay to Login in my Liferay Portal with wso2is user, but it not work for me in wso2is-5.4.1 and liferay6.2ga6. When I try login, liferay's log print "Primary URL :https://wso2is.local:9443/services/Secondary URL :null" but no call to wso2is server is done.
I added this lines into my portal-ext.properties :
auth.pipeline.pre=org.wso2.liferay.is.authenticator.WSO2ISAuthenticator auth.pipeline.enable.liferay.check=false wso2is.auth.service.endpoint.primary=https://wso2is.local:9443/services/ wso2is.auth.thrift.endpoint=localhost wso2is.auth.thrift.port=10500 wso2is.auth.thrift.connection.timeout=10000 wso2is.auth.thrift.admin.user=admin wso2is.auth.thrift.admin.user.password=admin wso2is.auth.thrift.endpoint.login=https://wso2is.local:9443/ wso2is.auth.thrift.system.trusstore=/wso2is-5.4.1/repository/resources/security/wso2carbon.jks wso2is.auth.thrift.system.trusstore.password=wso2carbon
Is there something wrong?
Unfortunately, a lot of the WSO2 documentation is very crufty, containing articles that have been pulled forward from previous versions of the documentation without regression testing on the use cases they present. In short, there's stuff in the documentation that plain doesn't work. If you look at the bottom of the article you'll see the following:
Please note that the above configuration is tested with Liferay 6.1.1
and WSO2 Identity 3.2.3/4.0.0.
I recall I tested this a long time ago, and determined that it wouldn't work with the current version, but that was so long ago that I can't remember why. In any case, the approach presented for integrating Liferay was offered at a time where Liferay didn't have the ability to use standardized authentication protocols like SAML. Now that it does, you probably want to do it in a standards compliant manner instead of using an authentication interface Liferay only promotes using for proprietary authentication systems.
My suggestion is that if you are using Liferay portal enterprise with LDAP that you use the built-in SAML connector. If you aren't using Enterprise, there are some compatible authenticator extensions in the extensions store that will also integrate with Liferay. If you configure Liferay to be a client against WSO2 and then integrate Liferay to LDAP on the backend, it also allows Liferay to be used as a user dashboard instead of the jaggery based one that comes in the product.
We have a requirement where user needs to login to portal with CAS (but SAML way). User can also login via login portlet of liferay.
We have few apps hosted on Intranet and few on Extranet. When user is in our office network, he should be able to login to all the apps via SSO. This includes apps which are hosted on extranet as well.
To achive this we want to use SAML with CAS.
By doing some research I understand that in this case CAS would be my IDP i.e. Identity provider and my apps on extranet would be SP i.e. service provider
Any idea how to proceed with it?
Any help is appreciated.
I have to do the same thing but using a LDAP too ...
I'm following this cookbook to achieve that, the second chapter talks about Authentication and Registration Process
I hope this would be helpful!!