ArcGIS Server provides a proprietary token-based authentication mechanism where users can authenticate themselves by providing a token instead of a user name and password. An ArcGIS token is a string of encrypted information that contains the user's name, the token expiration time, and some proprietary information. To obtain a token, a user provides a valid user name and password. ArcGIS Server verifies the supplied credentials and issues a token. The user presents this token whenever accessing a secured resource.
Jul 07, 2017 I am using ArcMap 10.5. I need to have a field where a unique ID is generated every time I add a point/polygon/feature. How would I go about doing this? I've tried some Python and VBA scripts seen on Geonet however they did not seem to work. Also, If I am able to get this working in ArcMap will that.
To maintain the security of the token, each token is associated with an expiration time. The end user may see a time-out or other error message if an expired token is used.
Tokens with shorter expiration times are more secure, as a token intercepted by a malicious user can only be used within a smaller time window. However, a short expiration time means that applications need to request new tokens more frequently.
Two parameters define the life-span of issued tokens:
An ArcGIS token is a string of encrypted information. The shared key is the cryptographic key used to generate this encrypted string. The more complex the shared key, the harder it is for a malicious user to break the encryption and decipher the shared key. If a user is able to decipher the shared key, replicate the ArcGIS Server encryption algorithm, and obtain the list of authorized users, the user will be able to generate tokens and consume any secured resource on that particular ArcGIS Server.
Before defining a shared key, consider the following:
To prevent the interception and misuse of tokens, the use of a secure connection using HTTPS is recommended. The use of HTTPS ensures that the user name and password sent from the client and the token returned from ArcGIS Server cannot be intercepted.
When building custom ArcGIS client applications that use GET requests to access web services secured using ArcGIS token-based authentication, it is recommended that the token be sent in the X-Esri-Authorization header instead of a query parameter. This prevents intermediaries on the network, such as proxies, gateways or load-balancers from being able to obtain the token. The example HTTP GET request below sends the token in the X-Esri-Authorization header:
If ArcGIS Server uses ArcGIS Server authentication and not Web-tier authentication (IWA, HTTP BASIC, PKI, etc) the standard HTTP Authorization header may be used instead of the X-Esri-Authorization header:
ArcGIS geoprocessing tool that creates a match table to be used with the Add Attachments and Remove Attachments tools.
This tool will go through each row for the input target dataset and compare the Key Field in this dataset to the names of files in the Input Folder. For each match that occurs, a record will be created in the output table that contains the ObjectID value from the Input Dataset and the name of the matched file (or optionally the full path to that file). When used in the Add Attachments and Remove Attachments tools the MATCHID field is used as the key field to link the files on disk to records in the input dataset.
If the Output Match Table location is a folder, the output can be created as a dBASE table by specifying a name with the extension .dbf, or can be created as an INFO table by specifying a name with no extension. If the output location is a geodatabase, the match table will be a geodatabase table (do not specify an extension).
Input dataset that contains records that will have files attached.
Folder that contains files to attach.
Table that will be generated which contains two columns: MATCHID and FILENAME.
The values in this field will match the names of the files in the input folder. The matching behavior will ignore file extensions, which allows multiple files with various file extensions to match with a single record in the input dataset.
For example, if the input Key Field value is lot5986, a file on disk named lot5986.jpg would match with this record.
This parameter is used to limit the files the tool considers for matching. If the file name does not meet the criteria in the file filter parameter it will not be processed and therefore will not show up in the output match table. Wild cards (*) can be used in this parameter for more flexible filtering options. Multiple semicolon-delimited filters can be used as well.
For example, consider a directory that contains the following files: parcel.tif, parcel.doc, parcel.jpg, houses.jpg, and report.pdf.
To limit the possible matches in this list to .jpg files, use *.jpg.
To limit the possible matches in this list to .pdf and .doc files, use *.pdf; *.doc.
To limit the possible matches in this list to files beginning with parcel, use parcel*.
To limit the possible matches in this list to files that contain the text arc, use *arc*.
Determines if the output match table field FILENAME will contain a full path to the dataset or only the file name.
The following code snippet demonstrates how to use the GenerateAttachmentMatchTable in the Python window.
The following stand-alone script demonstrates how to use the GenerateAttachmentMatchTable tool to create a match table that contains matches for only JPG and PDF files.
This tool does not use any geoprocessing environments.