We tried enabling SAML SSO on the Artifactory 7.35.1 with PingFederate but unsuccessful.
We have followed this documentation. Ping Authenticates successfully and redirects to Artifactory but Artifactory fails with the below error.
{"errors":[{"status":400,"message":"{"error":"Error occurred while trying to login using SAML. Check your Artifactory logs for more details."}"}]}
We tried to enable log following this guide but the "artifactory.log" file is not getting created and SAML XML is not logged to any of the log files as stated.
Appreciate any guidance to debug or fix the error.
Related
I have installed artifactory pro version 7.4.1. I have set up SAML SSO using Jumpcloud as the SAML Provided, but after trying to log in using SSO login page is throwing 403 forbidden error. Did not see any error in artifactory-service logs. can you please help on this issue.
I published my API service application to Azure cloud. I went into Azure api service console and tried tor run my service. Nevertheless i faced such error:
Unable to configure HTTPS endpoint. No server certificate was specified, and the default developer certificate could not be found
I was trying to follow the possible solutions from this topic:
Unable to configure HTTPS endpoint. No server certificate was specified, and the default developer certificate could not be found
I tried every given solution out of it like removing certificates, running dotnet commands etc but i still got this error and don't know what more can be done here. I am really stack on it. Can anyone help me out?
Hope the suggested solution by Maarten Dev has resolved your issue. I am converting this as an answer to help the other community members.
You can enable logging in the WebApp > Monitoring > App Service Logs blade. You can then view the logs using WebApp> Monitoring > Log Stream or by viewing the logs using FTP/Blob
I'm trying to integrate open distro ELK with OpenID Connect by following the guide here (https://opendistro.github.io/for-elasticsearch-docs/docs/security/configuration/openid-connect/#kibana-single-sign-on), specifically by updating the kibana.yml and config.yml files as shown.
The behavior I'm seeing is:
Visit ${KIBANA_URL}
Get redirected straight to ${KIBANA_URL}/auth/openid/login with 401
I'm checking the network requests, and I'm not sure why it's not redirecting to the IDP (Okta) first. What should I check next?
I have configured 2 wso2 IS server instances in the local windows environment according to the documentation provided https://docs.wso2.com/display/CLUSTER44x/Clustering+Identity+Server+5.1.0%2C+5.2.0+and+5.3.0
and also the NGINX configuration with self signed certificates
I have been redirecting to the wso2 is login page of any one node but when logging in its redirecting to the login page again but at log showing
[2017-05-24 15:52:26,528] INFO {org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} - 'admin#carbon.super [-1234]' logged in at [2017-05-24 15:52:26,528+0530]
Its working properly with one node(other is down).
I am not able to figure out where is the issue, both nodes are working properly no error in the logs,
Please help ,
Thanks
Pankaj
You will need to enable sticky sessions in nginx configurations. See WSO2 doc too.
I am using a tutorial: http://swift.openstack.org/development_saio.html
I'm currently trying to create a swift environment for some test, but got the following error when getting an X-Storage-Url and X-Auth-Token using test command.
UnauthorizedThis server could not verify that you are authorized to access the document you requested.
I am new for openstack, Ples help me..
Try Installing memcache in the server.
In Openstack swift Auth tokens are stored in memcache. So if memcache is not installed auth tokens are not stored which results in failure of authorization.