Proxy Authentication Error Invalid Name Provided
Contents |
D:\gradle\gradle-1.2\samples\java\quickstart>gradle gradle negotiate authentication error no valid credentials provided build :compileJava NEGOTIATE authentication error: Invalid name provided (Mechanism
Mechanism Level: Krbexception: Cannot Locate Default Realm
level: Could no t load configuration file C:\WINDOWS\krb5.ini (The system cannot find the file gradle authentication scheme 'all'(authentication) is not supported by protocol 'file' s pecified)) FAILURE: Build failed with an exception. What went wrong: Could not resolve all dependencies for configuration ':compile'. > Could not resolve
Invalid Name Provided (mechanism Level: Cannot Locate Default Realm)
group:commons-collections, module:commons-collections, versi on:3.2. Required by: :quickstart:1.0 Could not HEAD 'http://repo1.maven.org/maven2/commons-collections/commons-c ollections/3.2/commons-collections-3.2.pom'. Received status code 407 from serve r: Proxy Authentication Required Try: Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. BUILD FAILED Total gradle properties time: 4.406 secs Peter_Niederwieser (Peter Niederwieser) 2012-11-08 09:58:00 UTC #2 Can you double-check that you have correctly configured proxy authentication? m_m (m m) 2012-11-08 10:14:00 UTC #3 this is the gradle.properties which I have placed in the project root systemProp.http.proxyHost= systemProp.http.proxyPort= systemProp.http.proxyUser= systemProp.http.proxyPassword= systemProp.http.nonProxyHosts=localhost systemProp.http.auth.ntlm.domain= Peter_Niederwieser (Peter Niederwieser) 2012-11-08 10:18:00 UTC #4 Well, the values matter too. Did you use '[domain]/[username]' for 'proxyUser'? In that case, you don't have to set 'http.auth.ntlm.domain'. m_m (m m) 2012-11-08 10:34:00 UTC #5 I have tried both the options Option 1 : systemProp.http.proxyUser=UserName systemProp.http.auth.ntlm.domain=DomainName Option 2 : systemProp.http.proxyUser=DomainName/UserName Peter_Niederwieser (Peter Niederwieser) 2012-11-08 10:47:00 UTC #6 I've upgraded Apache HttpClient from 4.2.1 to 4.2.2. You'll be able to give it a try in tomorrow's nightly build. If that doesn't help, you may have to do some research on your own. Maybe
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags https://discuss.gradle.org/t/cannot-access-repositories-via-basic-auth-proxy/7601 Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Apache HttpClient 4.1.1 NTLM authentication not SPNEGO up vote 8 down http://stackoverflow.com/questions/5746545/apache-httpclient-4-1-1-ntlm-authentication-not-spnego vote favorite The problem here is consuming a web resource that has NTLM authentication while using the Apache HttpClient on the client side. The issue I am having is forcing the client to use NTLM authentication. here is a code sapmle. DefaultHttpClient httpclient = new DefaultHttpClient(); httpclient.getAuthSchemes().register("ntlm",new NTLMSchemeFactory()); NTCredentials creds = new NTCredentials("_myUSer_","_myPass_","_myWorkstation_","_myDomain_"); httpclient.getCredentialsProvider().setCredentials( new AuthScope("serverName",80), creds); List
Sessions Ideas Apps Consulting Developers Jobs Answers Help & Training Events https://success.salesforce.com/answers?id=90630000000ghEMAAY Collaboration Ideas Featured Groups Known Issues New here? Sign Up https://issues.jasig.org/browse/EMAILPLT-149 Have an account? Sign In Browse by categories All Collaboration Configuration & Data Management Customer Service & Support Desktop Integration Email Email Marketing Journey Management Mobile Mobile Messaging Packaging, Uploading & Installing Apps Reports & Dashboards Sales & Marketing authentication error Security Social Marketing Additional Products Ask Search: Reset Search Welcome to Support! Search for an answer or ask a question of the zone or Customer Support. Need help? Dismiss ShowAll Questionssorted byDate Posted ShowAll QuestionsUnanswered QuestionsUnsolved QuestionsSolved Questions sorted byDate PostedRecent ActivityMost Popular Unsolved QuestionsThis Question padmini Sidugondecommandline invalid name provided proxy authentication issueI am getting below error when i am import data from csv file to sfdc in apex dataloader commandline.C:\Program Files\salesforce.com\Data Loader\bin>process.bat "C:\DLTest\Command Line5\Config" extract2013-04-03 12:03:45,484 INFO [main] controller.Controller initLog (Controller.java:388) - The log has been initialized2013-04-03 12:03:45,500 INFO [main] process.ProcessConfig getBeanFactory (ProcessConfig.java:103) - Loading process configuration from config file: C:\DLTest\Command Line5\Config\process-conf.xml2013-04-03 12:03:45,812 INFO [main] xml.XmlBeanDefinitionReader loadBeanDefinitions (XmlBeanDefinitionReader.java:315) - Loading XML bean definitions from file [C:\DLTest\Command Line5\Config\process-conf.xml]2013-04-03 12:03:45,984 INFO [extract] controller.Controller initConfig (Controller.java:326) - config dir created at C:\DLTest\Command Line5\Config2013-04-03 12:03:46,062 INFO [extract] controller.Controller initConfig (Controller.java:354) - The controller config has been initialized2013-04-03 12:03:46,062 INFO [extract] process.ProcessRunner run (ProcessRunner.java:116) - Initializing process engine2013-04-03 12:03:46,062 INFO [extract] process.ProcessRunner run (ProcessRunner.java:119) - Loading parameters2013-04-03 12:03:47,406 INFO [extract] config.LastRun load (LastRun.java:96) -Last run info will be saved in file: C:\DLTest\Command Line5\Config\extract_lastRun.properties2013-04-03 12:03:47,421 INFO [extract] process.ProcessRunner run (ProcessRunner.java:127) - Logging in to: https://login.salesforce.com2013-04-03 12:03:47,421 INFO [extract] client.PartnerClient login (Par
authentication error: Invalid name provided (Mechanism level: Cannot locate default realm) for EWS protocolAgile Board ExportXMLWordPrintable Details Type: Bug Status: Resolved Priority: Minor Resolution: Fixed Affects Version/s: None Fix Version/s: 2.1.0 Labels: UOSS13Q3 Description When using EWS, for each message sent you see in the logs: WARN [uP-PortletExec-7-admin-RESOURCE-[exchange-email-preview]] o.a.h.c.p.RequestTargetAuthentication 2013-08-27 16:09:57,167 - NEGOTIATE authentication error: Invalid name provided (Mechanism level: Cannot locate default realm) See attach message trace. Suggested solutions: 1. Ideal solution: Configure http client to only support NTLM v2 Auth (and maybe Kerberose if there is a default implementation) so there is only 1 Auth attempt instead of 3. May not be able to do this; may need to try NTLM first to get response that includes WWW-Authenticate NTLM header that has string that's included in POST to indicate NTLM v2). See http://hc.apache.org/httpcomponents-client-ga/tutorial/html/authentication.html 2. Configure http client to exclude Negotiate? 3. Configure logback.xml (with documentation explaining why, referring to this issue) to set log level to ERROR. Not as ideal because there may be some other WARN messages from that class that are useful. OptionsSort By NameSort By DateAscendingDescendingDownload AllAttachments EMAILPLT-149 Message Trace.txt 29/Aug/13 3:26 PM 14 kB James Wennmacher Activity Ascending order - Click to sort in descending order All Comments Work Log History Activity Transitions Hide Permalink James Wennmacher added a comment - 04/Sep/13 12:56 PM - edited Added to logback.xml in 2.1.0 to temporarily hide this error message. We should still look into reconfiguring the authentication mechanism or whatever is the appropriate solution to this issue.