georchestra/ckanext-georchestra

geOrchestra extension for CKAN (not actively maintained)

geOrchestra

geOrchestra is a complete Spatial Data Infrastructure solution.

It features a metadata catalog (GeoNetwork), an OGC server (GeoServer) with fine-grained access control (based on GeoFence), an advanced viewer and editor and many more (security and auth system based on proxy/CAS/LDAP, analytics, admin UIs, ...)

Please refer to the documentation for more information.

ckanext-georchestra's Issues

Optimize synchronization process

For now (v0.2.1), when LDAP DB has hundreds of orgs & users, it takes quite some time, and possibly resources.

• benchmark sync resource consumption
• implement incremental sync: check changes in LDAP since last sync, would reduce a lot the nb of entries to sync at each run. 1 full sync run /week would be sufficient, to keep safe from divergence, and incremental syncs in-between

user id problem with special characters

j-pommier and j.pommier users in geOrchestra would both be translated as j_pommier in CKAN

geOrchestra and ckan don't enforce the same rules for user id definition.
geOrchestra accepts - and . in the user ID (but not _)
CKAN accepts _ but not - or .
In its current state, this extension translates . and - into _. Which could lead to an id collision.

get rid of synchronization: rewrite user & org actions to tap directly into LDAP

It may be possible to rewrite all get actions upon organization & user, to read directly in the LDAP DB, and shunt totally the user & orgs management in CKAN and in CKAN DB. This would probably be more robust & more efficient than what's coded for now

Accessing a protected page redirects to CKAN login page rather than CAS login page

eg /ckan/harvest/pigma/job/f91b5115-e16d-4455-9047-1fd9922e4f82 redirects to /user/login?came_from=http%3A%2F%2Ffqdn%2Fharvest%2Fpigma%2Fjob%2Ff91b5115-e16d-4455-9047-1fd9922e4f82

Expected : /ckan/harvest/pigma/job/f91b5115-e16d-4455-9047-1fd9922e4f82 redirects to /ckan/harvest/pigma/job/f91b5115-e16d-4455-9047-1fd9922e4f82?login which will be interpreted by the SP.

"profile updated"

/ckan/dashboard/ shows

But I'm pretty sure @jeanpommier 's work on LDAP sync will solve this issue.

Missing CKAN_LDAP_URL

CKAN currently has the ability to configure itself through ENV vars.
This is very convenient. See https://docs.ckan.org/en/ckan-2.7.3/maintaining/configuration.html#environment-variables

What is now missing with this extension is the ability to get CKAN_LDAP_URL from an env var.