Latest Contributions by Luis_DiegoVargas1

Hello, I had this “issue” a few days ago, and I'd like to share the workflow. Scenery: The input it’s a JSON, was obtained through a REST and looks like this. The first value in the array it’s a Double, the second and third are a Boolean (is important that the types of values in the array are different).   The Output it’s a Feature Service running in ArcGIS Server (10.7.1). Fields: objectid ( type: esriFieldTypeOID, alias: OBJECTID, nullable: false, editable: false ) username ( type: esriFieldTypeString, alias: username, editable: true, nullable: true, length: 25 ) userid ( type: esriFieldTypeDouble, alias: userID, editable: true, nullable: true ) lng ( type: esriFieldTypeDouble, alias: lng, editable: true, nullable: true ) lat ( type: esriFieldTypeDouble, alias: lat, editable: true, nullable: true ) alt ( type: esriFieldTypeDouble, alias: alt, editable: true, nullable: true ) speed ( type: esriFieldTypeDouble, alias: speed, editable: true, nullable: true ) heading ( type: esriFieldTypeDouble, alias: heading, editable: true, nullable: true ) lastseen ( type: esriFieldTypeString, alias: lastSeen, editable: true, nullable: true, length: 25 ) sos ( type: esriFieldTypeString, alias: sos, editable: true, nullable: true, length: 10 ) low_battery ( type: esriFieldTypeString, alias: Low_Battery, editable: true, nullable: true, length: 10 )   The values that interest me most are those found within the arrangement called Speed (it’s just a random value, the idea is that the first value is a Double), SOS and Low Battery (these are Boolean type).   {     "id": -1,     "result": [         {             "records": [                 {                     "fieldName": "Speed",                     "fieldID": 33,                     "value": 3.0558000006926482,                     "valueType": "System.Double"                 },                 {                     "fieldName": "SOS",                     "fieldID": 20,                     "value": true,                     "valueType": "System.Boolean"                 },                 {                     "fieldName": "Low Battery",                     "fieldID": 24,                     "value": true,                     "valueType": "System.Boolean"                 }             ],   The “Issue” GeoEvent automatically takes the first value of the array as the default value for all the definition values in the array, in this case the first value it’s a double.   {     "id": -1,     "result": [         {             "records": [                 {                     "fieldName": "Speed",                     "fieldID": 33,                     "value": 3.0558000006926482,                     "valueType": "System.Double"                 },   So, this cause that the other values (Boolean) was not identified correctly. Then this makes the remaining values (Boolean) can’t be "read" and have a null value in the service. If in the definition we defines Boolean instead of Double as the default value type, the double values does not work.    The alternative: Is making a change in the definition and define the values as String.   Once this change has been made, the updates to the service are done correctly.   The Field Mapper looks like this. This the result: objectid: 10 username: TrackerOne1 userid: 14.0 lng: -84.05072 lat: 9.93914 alt: 14.0 speed: 3.8892 heading: 14.0 lastseen: Mon Aug 26 10:24:06 CST 2019 sos: false low_battery: true Point: X: -9356483.351208016 Y: 1112011.1996998154   Regards. ... View more

Hello, We have an application written in C# which performs user authentication to generate a Portal (10.6) token, this token its used to insert points in a Feature Service, get organization nfo etc. In the past, the "normal/traditional" authentication model using Portal users works fine, the issue is that the environment changes, and now use domain users (Active Directory) and Single Sign-On (SSO) / Integrated Windows Authentication (IWA) for all the Portals users, this change in the IIS has affected this process and now we have the error 401, which is caused for use with authentication method. Has anyone implemented this in the past and knows how to do it? I have tried several alternatives (Negotiate and NTLM) and they have not been functional. This is the code used:       private string _getResponse(NameValueCollection data, string url)     {         string responseData;         var webClient = new WebClient();         var response = webClient.UploadValues(url, data); -> Here we have the 401 error.         responseData = System.Text.Encoding.UTF8.GetString(response);         return responseData;     }     public string GetToken(string username, string password)     {         var data = new NameValueCollection();         data["username"] = Username;         data["password"] = Password;         data["referer"] = "https://domain.local/portal";         data["f"] = "json";           TokenInfo x = JsonConvert.DeserializeObject<TokenInfo>(_getResponse(data, "https://domain.local/portal/sharing/rest/generateToken")); -> Here we have the 401 error.         return x.token; ;     }       private organizationInformation _getOrgInfo(string token)     {         var data = new NameValueCollection();         data["token"] = token;         data["f"] = "json";           organizationInformation x = JsonConvert.DeserializeObject<organizationInformation>(_getResponse(data, "https://domain.local/portal/sharing/rest/portals/self")); -> Here we have the 401 error.         return x;     }       private string _getResponse(NameValueCollection data, string url)     {         string responseData;         var webClient = new WebClient();         var response = webClient.UploadValues(url, data); -> Here we have the 401 error.         responseData = System.Text.Encoding.UTF8.GetString(response);         return responseData;     }   Regards. ... View more

Hello, When the user and group stores are set to WINDOWS, the @DOMAIN is always added to the end of the enterprise usernames that are added through "Add members based on existing enterprise users".  When you switch to LDAP, you have more flexibility because you can set this attribute; but, I can customize this username? or concat some attributes? or adding more attibutes? (this JSON dont work, its just an example). {   "type": "LDAP",   "properties": {     "userPassword": "abcd123",     "caseSensitive": "true",     "userEmailAttribute": "mail",     "usernameAttribute": "sAMAccountName+@DOMAIN",     "user": "domain\\user",     "userFullnameAttribute": "cn",     "ldapURLForUsers": "ldap://1.1.1.1:389/DC=domain",     "isPasswordEncrypted": "false"   } } The idea, its that the end user will login with the same structure that using WINDOWS authentication, username@DOMAIN We have a end user with two portals, one using WINDOWS authentication and other in the DMZ running on Linux, and they want use the same username for both (username@DOMAIN). Regards. ... View more

Hello, This end user are unable to view status, inputs/outputs or edit GeoEvent services, they are using 10.5.1. Have you guys seen this before? and solved this issue? We have tried to reset the configuration and reload it, but it still has this behavior. Something interesting is that in the manager it indicates that it is running but it is not. Regards. ... View more