I have created REST services using RESTEasy and generated certificate using openssl and configured with https from this JBoss link. When I try to consume the service like this,
ClientRequest request = new ClientRequest("https://localhost:8443/services/users");
request.accept(MediaType.APPLICATION_XML);
ClientResponse<Result> response = request.post(Status.class);
I got "Peer not authenticated" exception. In google I saw this error and people suggested to use Apache Http Client. But I am using RESTeasy client to consume the service. How I can avoid this error?
The Nexus OSS behavior was inconsistent. First I thought this is due to permission settings. So I ran the tomcat as Admin, but still got the same error. Spent lots of time and no clue. Moved to use Archiva for maven repo. Dont take me wrong, Nexus OSS UI is much much better than Archiva. But Archiva is working without any problem.
After 6 months again tried to setup Nexus OSS with new version. Still same error. This is something how Nexus OSS connects to internet. Finally changed the Nexus OSS network connection settings. Configured the proxy & NTLM authentication. After that it is working fine.
Still its a mistery why nexus oss didnt work with default configuration while archiva works.
Related
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.
Im in the process of evaluating the new interface of Apache Archiva. The user interface is really good and I was able to configure most of the settings.
However, when I try to deploy the artifact through eclipse Im getting the below error.
Error code 405, HTTP method PUT is not supported by this URL
I donot get this when I use the Apache Archiva 1.3.6.
Any idea?
This can happen if your repository URL is incorrect. See GitHub issue 4.
I have setup the new Archiva version 2.0.0. Apparently this issue has been fixed with the latest version.
I am using Atlassian JIRA™ (Professional Edition, Version: 3.0.3-#75 and Netbeans IDE 7.1
But when trying to validate a connection to Jira from netbeans it gave me this error "Jira RPC services are not enabled"
while I have enabled it and also I enabled allow remote calls in Jira
To be more specific "RPC JIRA Plugin" that I have installed is
The standard JIRA RPC services, both SOAP and XML-RPC.
Plugin Version: 1.1
JIRA version: 3.0
It has
System XML-RPC Services (xmlrpc)
The standard JIRA XML-RPC services.
RPC Field Coordinator (rpcFieldCoordinator)
Issue Service (issueService)
User Service (userService)
Token Manager (tokenManager)
System SOAP Services (soap)
The standard JIRA SOAP services.
Magic Field Validator (magicFieldValidator)
Project Service (projectService)
My global configurations are:
Allow users to vote on issues ON
Allow users to watch issues ON
Allow unassigned issues ON
Cache issues ON
External user management OFF
Logout Confirmation Never
Use Gzip Compression OFF
Accept remote API calls ON
BTW, it is not just netbeans, I got same problem with other tools as well to connect to jira
I will apreciate if my answer be found ASAP .
Thanks
Answering an old question, but I thought someone else might find this useful.
I got the same error today setting up an issue tracker in NetBeans 7.2 and I eventually tracked it down to NetBeans not being able to correctly resolve (using DNS) the (local) host name that was running our JIRA server. When I changed NetBeans to use 'No Proxy' in the main settings, it worked fine.
EDIT: Note that as of version 7.0 of the JIRA server, Atlassian have depracated the SOAP/XML-RPC API, so the JIRA Plugin for Netbeans no longer works. :-(
I'm trying to host nuget on my Amazon EC2 VPS, and I'm having issues.
I've followed the instructions here ( Hosting your own NuGet Feeds )
I've read this thread ( NuGet: remote server returned an Error(403) Forbidden ) along the same lines.
I'm not running TFS
It "could" be a proxy issue, but I'm not entirely sure how to check.
My NuGet feed is located at http://nuget.infinitas.ws. You'll notice that both http://nuget.infinitas.ws/nuget/Packages and http://nuget.infinitas.ws/Packages are throwing errors.
Any help with this will be greatly appreciated.
You are probably running the NuGet.Server in a Web Site-project. Try to run it via an ASP.NET Web Application instead (in Visual Studio you can create one via File -> New -> Project -> ASP.NET Web Application)
Have you tried the latest version (1.5)?
The release notes include some changes related to proxy authentication:
Support for Proxies that require authentication
When using NuGet behind a proxy that requires authentication, NuGet will now prompt for proxy credentials. Entering credentials allows NuGet to connect to the remote repository.
I realize I'm a little late to the party but I've just spent a frustrating couple of hours with the same problem.
I found that switching the Application Pool from "Classic" to "Integrated" fixed the problem