Latest Contributions by NimeshJarecha

Hi Frank, Like 100.x SDK, the credential property is not available in 200.x SDK. Please refer the Migrate authentication from 100.x to 200.x  doc for all the differences.  You can create the credential and add it to the store before creating and loading the service feature table. let tokenCredential = try await TokenCredential.credential( for: URL(string: "<service feature table url>")!, username: "username", password: "password" ) ArcGISEnvironment.authenticationManager.arcGISCredentialStore.add(tokenCredential) let table = ServiceFeatureTable(url: URL(string: "<service feature table url>")!) try await table.load()   Hope this helps!   Regards, Nimesh ... View more

Hi Abhishek, Thank you for your interest in the ArcGIS Maps SDK for Swift. The production release for the Swift SDK is expected to be sometime next week. So I would suggest getting started with current beta release and switch to production release when it is out.  Regards, Nimesh ... View more

Hello Andriy Fedin, Based on the error information provided, either the server or the additional security layer is engaging in the `Client Certificate` challenge. Could you please elaborate on the security setups on your environments? Error Domain=com.esri.arcgis.runtime.services.error Code=401 "Credential Required" UserInfo={NSURL=https://<NDA_domain.com>/FeatureServer/4, NSLocalizedDescription=Credential Required, protectionSpace=<NSURLProtectionSpace: 0x600000980f10>: Host:<NDA_domain.com>, Server:https, Auth-Scheme:NSURLAuthenticationMethodClientCertificate, Realm:(null), Port:443, Proxy:NO, Proxy-Type:(null)} Also, you can please create request log by setting properties on request configuration. You can send the log file to me directly.  let config = AGSRequestConfiguration.global() config.debugLogFileURL = URL(fileURLWithPath: "<path>/requestLog.md") config.debugLogDeleteBeforeEachRun = true config.debugLogRequests = true config.debugLogIncludeRequestHeaders = true config.debugLogResponses = true config.debugLogIncludeResponseHeaders = true   Regards, Nimesh   ... View more

You can try following steps, 1. Set `AGSAuthenticationManager.delegate`. 2. In the delegate implement authenticationManager:didReceiveAuthenticationChallenge: 3. When challenge is issued for the portal, get the token through your custom implementation. 4. Create AGSCredential with generated token. 5. On the `AGSAuthenticationChallenge` object call, continueWithCredential: If this works, the only problem will be that we'll not be able to automatically refresh token when it expires. Regards, Nimesh  ... View more

Hi Shimin,   Thank you for the new log file. I analyzed the log file and particularly the HTTP responses and response headers. Based on that looks like your server setup has load balancer. The responses with response header Server = "" are working fine and responses which has Server = "awselb/2.0" are responding the HTTP status code 403. The response code 403 is considered as an authentication error and we prompt for the credential. You will have to figure out why that server responds with HTTP status code 403.   Regards, Nimesh ... View more