You can change the password via the web interface by going to the Users,Groups, and Roles link:
Once there, go to the Users/Groups tab and select the user which you want to edit
You can then change the passwords or any other details you need to change.
The gdal OpenFileGDB driver was reversed engineered.. I guess this reverse engineering didn't include the licensing component! Suffice to say - if current versions of gdal can freely open this data, I don't think there's any way you can prevent savvy users from doing that.
I found a solution that worked for me.
I change setting in the register. Search for 1201 and value 0 (DWORD) at:
Problem running any tool (on Esri's Geonet forums)
This - in my humble opinion - seems to be a "false positive". I uploaded it to virustotal.com and 0 of 56 scanners gave an error (last analyis ~ 2month ago). I forced virustotal to reanalyze the file and now one scanner from 56 scanners gave an alert : Kapersky.
You should send the file to Kapersky for analysis, so they can update their virus-definition ...
The one important difference that most suggestions omit, and very possibly this is all that's needed to fix this, is that in Zone 0 a new DWORD 1201 MUST be created if it doesn't already exist. In other words changing all the other DWORD values to "0" will not work unless 1201 is also added.
The solution can be found here: https://geonet.esri.com/ideas/...
Quick and short solution:
Please follow this post: REDIRECT: axtiveX error warning
I found a fix for this on ESRI's web site - axtiveX error warning. A staff member came into the thread and confirmed it is a bug in current versions of ArcGIS (at time of writing, 10.5.1 was the latest).
So far we have only seen it affect our 1703 users. ...
There is this blog post (in french, dated june 2015) that explain that the data are not encrypted but merely renamed with the prefix ''GDB_SecureCopy'' that ESRI product doesn't seem to by able to see or open without the licence file.
As Qgis (at this time 2.8) was able to open it (in less time that it would have taken to install the licence file to open ...
I finally found what I was looking for: a proper ArcGIS Server web endpoint that I could use to generate tokens!
The call is this:
which gives back the token into the HTTP response body, and one ...
Your best bet is going to be not saving the db credentials in your project (QGIS even gives you a warning on the potential danger of saving your credentials when you first add the db).
When you open the project, you'll immediately be prompted for your credentials before any layers from the db are rendered.
Alternatively, you can:
Use OS methods to hide/...
Yes, it is a security problem.
A common solution is to go through a proxy- a service you write that your client can call that will in turn call the endpoint. Your client calls your service with all arguments except the token. The service copies all the arguments passed to it, adds the token, calls the endpoint, and returns the response to your client.
Unfortunately, these false alarms happen from time to time, for example
[Qgis-user] BitDefender detects Malware in QGIS 2.14
[Qgis-user] False positive with norton + whitelisting
As Kurt already mentioned correctly, it is best to inform the antivirus provider.
The situation is much improved. The organisation admin can create a group with Members can update items permission. This removes the need for shared login credentials and/or giving all editors organisation-wide admin privileges*, while also making group permissions answer** viable for public maps.
The new recommended practice is:
Please have a look at How ArcGIS Server Security works.
Basically, you will need to make users and groups, and give a particular User rights over certain services.
I wouldn't do this, especially not with some home-brewed license "server".
If you're certain your IP is valuable enough to protect by licensing, you should purchase a commercial licensing solution.
But I don't think this is necessarily the best solution as any form of DRM only inconveniences legitimate users and will not stop determined people reverse ...
I used to work for a Government client, that had a similar request. I tried to reason with them, but ...
There is typo in your url
You can use basic auth to make the requests:
As stated in GIS-Jonathan's answer this can be accomplished by setting the file permissions to Read-only.
In windows 7 you can accomplish this by navigating to the file in windows explorer, right clicking the file with the .shp extension and clicking 'properties'. There should be two checkboxes near the bottom of the properties window that say 'Read-only' ...
If you are using arcpy functions in python to connect to your SDE instance, then you could create an SDE connection file with OS authentication. This SDE file does not store any credentials but uses the credentials of the executing user. Then you can set up the scheduled task to run as a user with the correct DBA credentials. Windows task scheduler will ...
The "ArcGIS-101SP1-S-SSEC-Patch-lx" patch should be applied to 10.1 SP1, not just 10.1 (10.1 SP1 is a standalone install, not something to be applied to 10.1). There are more recent patches posted on support.esri.com -- I recommend you keep up to date.
Choosing to upgrade ArcGIS Server should be part of a process that includes ArcGIS Desktop upgrades ...
Depending on what you need to be exposed to the internet, it might be the easiest just to change the connector port of the Connect Tomcat to 80 in
C:\Program Files\Pitney Bowes\SpectrumSpatialAnalyst\Tomcat7\AnalystConnect\conf\server.xml
Below are some further notes (assuming Windows server). You may also contact the PB tech support team if you continue ...
You can change the admin user name to something other than admin. This doesn't upset Geoserver (i.e. it is not reserved). I have never seen any recommendation saying you should do this, but, to my way of thinking, changing the admin user name to something less obvious is a tiny little bit of extra security (giving a hacker two things to guess/crack). I do ...
Out of the box, ArcGIS Server comes with two pieces of functionality you might explore:
Feature services have ValidateSQL request available which can check your SQL query/statement.
validateSQL also prevents SQL injection. In addition, all table and
field names used in the SQL expression or WHERE clause are validated
to ensure they are valid tables ...
GeoServer does not do anything to control the permissions of the directories, so it gets the default permissions the OS would assign.
I believe you have to change the umask for the user that's running the GeoServer process: http://www.cyberciti.biz/tips/understanding-linux-unix-umask-value-usage.html
I added alread a FeatureRequets for this on ideas.esri.com:
ArcGIS Server: New role like 'mapservice-manage' to associate on a folder and/or mapservice
Just vote for it. May be it will be considered :-)
You can't really do this at the SQLite / SpatiaLite / QGIS level. You can do it at the filesystem level (e.g. by setting permissions or access control lists on the file) by only allowing one user (typically the file owner) to write to it, and everyone else only read access.
How to do that isn't really a GIS question, but for completeness:
On Linux or ...
There isn't really going to be a great solution.
If you put your site behind SSL and made your data stuff that your script downloads through AJAX calls, then at least you don't have your data right there in the page or script source nor is it available to packet sniffers but someone could run your page in a script debugger such as Chrome offers and they ...
The sample linked by Devdatta, while valid, is the pre-Identity Manager way of doing this and involves a lot more code that is necessary now that authentication for ...
You can limit editing by user so that users only edit their features:https://doc.arcgis.com/en/arcgis-online/share-maps/manage-hosted-layers.htm
For user specific data access controls I have seen a demo where the server dynamically filters the response data based on authenticated user. This was done with custom ArcGIS Server SOE developed by Esri ...
As a workaround you can include extra parameters into the WMS server base URL. Remember also to check the "Ignore GetMap URI reported in capabilities". If username and userkey are changed you must edit the WMS connection details accordingly. Standard does not say either that WMS clients should keep the vendor parameters. Make a feature request for QGIS and ...
I believe that the url you provide to the QgsRasterLayer needs to be url encoded.
Otherwise it seems that the url parameter which you pass to the QgsRasterLayer splits upon the '&' character.
The following snippet demonstrates the creation of a QgsRasterlayer for Cochlearia danica L.
wmsService = 'https://gis.nbn.org.uk/SingleSpecies/NBNSYS0000002854?...