Skip to main content

Security

Permissions, roles, and administration. Security in data processing.

  • 166 Posts
  • 511 Replies
166 Posts
D
dgfip-fr
asked in Security
hkingsbury
Celebrity
hkingsburyCelebrity
asked in Security
Y
ymotake
asked in Security
john.beck
Contributor
john.beckContributor
asked in Security
jbradfor
Contributor
jbradforContributor
asked in Security
oliver.morris
Contributor
oliver.morrisContributor
asked in Security
francis
Contributor
francisContributor
asked in Security
Security issue with database connections/web connections

You can set security on database/web connections but the admin user has the permission to view, use and execute by default. Assume that a user knows the name of a secure database connection on the server and use that same name in his workbench as a private parameter with different parameters but with the same as the secure connection on the server. When the user upload his workbench to the server, he will not be able to execute the workbench on the server because he doesn't have the permission to use the database connection on the server. But he asks to schedule his workbench and the admin user configures the schedule for this workbench. From that moment the workbench is able to use the database connection on the server because the admin user has the permission to use the secure database connection.A solution could be that the schedule is configured by another user than admin. Is there any other way to handle this security issue?We are running FME Ser

300
david_r
Celebrity
M
misazab95
asked in Security
How can i upload license file via API?

I´m executin this command to upload the FME license: curl -X POST "https://localhost:443/licensing/license?filetype=fmelic" -H "Authorization: fmetoken token=****" -H "Content-type: application/octet-stream" -H "Accept: application/json" --data "@fme_license.fmelic" But i got this error:<!doctype html><html lang="en"><head><title>HTTP Status 404 – Not Found</title><style type="text/css">body {font-family:Tahoma,Arial,sans-serif;} h1, h2, h3, b {color:white;background-color:#525D76;} h1 {font-size:22px;} h2 {font-size:16px;} h3 {font-size:14px;} p {font-size:12px;} a {color:black;} .line {height:1px;background-color:#525D76;border:none;}</style></head><body><h1>HTTP Status 404 – Not Found</h1><hr class="line" /><p><b>Type</b> Status Repo

261
H
B
bgogulapati
asked in Security
adamdunlap
adamdunlap
asked in Security
mattwilkie
Enthusiast
mattwilkieEnthusiast
asked in Security
nissedahlsten
Contributor
nissedahlstenContributor
asked in Security
clowncutie
Contributor
clowncutieContributor
asked in Security
langdonms
Contributor
langdonmsContributor
asked in Security
M
melvin
asked in Security
lobsterboy
lobsterboy
asked in Security
stuart.voerman
Contributor
stuart.voermanContributor
asked in Security
takashi
Celebrity
takashi
asked in Security
FME Server 2020.0 requires manually fix API Token Permissions after restoring configuration?

Hello,I upgraded FME Server from 2019.2 to 2020.0, and restored the configuration by importing the backup file which has been downloaded before uninstalling the previous version.Some of existing workspaces are run via API (request from a web page) and access a PostgreSQL database to read features with a FeatureReader, execute a SQL query with a SQLExecutor and so on.What I observed is, after upgrading to 2020.0, the workspaces failed to access the PostgreSQL database and logged this error message.FME Server error: `FME Server error: `Unauthorized request by user due to lack of proper permissions.'I was able to resolve the failure by manually adding access permission for the database connection to the API token, but it's a bit troublesome if you need to check and fix permissions of every Token whenever upgrading FME Server.I upgraded the FME Server several times before (FME 2019.0 -> 2019.1 -> 2019.2), but I didn't need to m

1238
H
C
cfinley
asked in Security
G
gponeconsulting
asked in Security
krien
Contributor
krienContributor
asked in Security
FME Server 2019 vs 2018 Generating Tokens within expiration period

Hi,Managing Tokens has changed in FME Server 2019 vs 2018 and I noticed the url for generating a Token with an expiration of 3 days without an update does not deliver the same token in 2019 in contrast to version 2018.The url used has the format:https://<fmeserver>/fmetoken/generate.json?user={{FMEUSER}}&password={{FMEPW}}&expiration=3&timeunit=day&update=falseand creates a new token (with a new 3 days expiration) every time in FME Server 2019 in contrast to 2018 where is returns the same token within the expiration period.I’ve searched for some kind of equivalent url, but haven’t found it yet.Is it still possible to get the same token during the expiration period in 2019 and what (service( url should I use?Kind regards, Krien Guijt

674
krien
Contributor
sigtill
Supporter
sigtillSupporter
asked in Security
L
lbohy
asked in Security
B
brianapeters
asked in Security
nag
Contributor
nagContributor
asked in Security

Badge Winners

  • Student (Grey)
    crbhas earned the badge Student (Grey)
  • Webinar Watcher (Grey)
    ewoonkhas earned the badge Webinar Watcher (Grey)
  • Welcome Back
    ewoonkhas earned the badge Welcome Back
  • Online Training
    aclarkhas earned the badge Online Training
  • FME Form Basic Training
    quentinvdshas earned the badge FME Form Basic Training
Show all badges

Community Stats

32,413
Posts
122,925
Replies
40,129
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.