OpenAM exportmetadata giving ERROR: No matching entity metadata found - metadata

I had Deployed OpenAM before in my machine and was able to work on it, For Saml Implementation
I was using the link : http://localhost:8080/OpenAM-13.0.0/saml2/jsp/exportmetadata.jsp to export the metadata. It was working fine in my machine.
But now after deploying the same war in someone's else machine when i go to the same link i get ERROR: No matching entity metadata found.
Please help, not able to get any idea what is wrong
-regards Joydeep

I had to create a Hosted IDP into OpenAM giving the link http://localhost:8080/OpenAM-13.0.0/ Now its working. Thanks #Bernhard

Related

Web service consumer SOAP version is showing error by default

I am trying to configure a SOAP service using web service consumer, as soon as I click on new configuration in the connector configuration, I see SOAP version column is turning into error and when I hover on it, it is showing some tooling related error and when i check my tooling stats in preferences, it shows in running state.
My studio version is 7.11.1
Please let me know how to resolve this issue.
The information is not complete to identify the root cause. Having said that it is possible that the error is happening when the Web Service Consumer connector is trying to download the WSDL if the access is restricted in some way. For example if the server has whitelisted the IPs of authorized clients, or there is an access restriction in your network, or some other permission issue.
In that case you may resolve the issue if you can download the WSDL locally and add it to the application in the src/main/resources folder, and reference it by the file name (with no path) instead of an URL.

SAML stopped working after update to Artifactory 5.3.1

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!

"the system cannot find the file specified" facing this error on deploying a web service to IIS8

We have recently deployed a web application and a corresponding web service to the IIS8 environment.
The web service builds perfectly fine on local and accesses the .pfx file from the shared path. The path mentioned in the web.config is something like this - \\Servername\Applications\ApplicationName\key.pfx.
However, on accessing the Web service after deploying it to the IIS8 server, it is throwing an exception as 'The System cannot find the file specified' while it is trying to read the .pfx file.
I searched several answers posted in this site as well as other forums but didn't get any proper resolution.
Would be really glad if someone can help me on this. Thank you.
Make sure that your path mentioned in the web.config are valid and the name of controller is the same in your application..
Look at :
firewall settings from the web server to the database server
connection string errors..

Unable to Integrating WSO2 Identity Server with Liferay for Authentication

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.

NuGet.Server Bad Request

I am currently trying to setup a NuGet server on our intranet but I'm having a problem. I'm following the instructions here:
http://docs.nuget.org/docs/creating-packages/hosting-your-own-nuget-feeds
The website works fine, but when I try to point the package manager at the source I get an error:
"Could not connect to the feed specified at 'myserver/DataServices/Packages.svc'. Please verify the package source (located in the Package Manager Settings) is valid and ensure your network connectivity."
The URL is correct, copied from the website and is "http://myserver/nuget".
Using Fiddler I inspected the data transfer and I get:
<error xmlns="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata">
<code></code>
<message xml:lang="en-AU">Bad Request - Error in query syntax.</message>
</error>
There are no error logs I can find on the server.
Can anyone help with this? I'd really like to use NuGet.Server but I'm out of ideas.
Thanks
Are you running the lastest versions of both the NuGet.Server and the Package Manager in VS?
Have you installed ASP.NET MVC 3 on the server?
Are you pointing the client directly at the base URL, or at the .svc endpoint? You should use the base URL - the call semantics have changed recently.