Trying to make an ldap attribute to a drupal role fails because the Authorization does not save the ldap_authorization synchronization items mentioned in dev issue/commit: https://www.drupal.org/project/authorization/issues/3168031
While I understand 4.x is -dev and not officially supported. I'm trying to recreate a Drupal7 site that uses 7.x-2.x at this time in Drupal 8.9.x and 4.x-dev seems like the only option to get me there at this time.
* install -dev or sable ldap module
For documentation purposes, 1 solution this can be fixed until a new stable Authorization module release is made on a per project basis using composer aliasing to assure you fake-out the correct -dev Authorization commit version as the current stable release.
Example composer.json snippet:
"require": {
"composer/installers": "^1.2",
"cweagans/composer-patches": "^1.6",
"drupal/authorization": "1.x-dev#6fbcf03c035a2c4ffcad6978991f6510f1407f48 as 1.0.0-beta4",
"drupal/core-composer-scaffold": "^8.9",
"drupal/core-project-message": "^8.9",
"drupal/core-recommended": "^8.9",
"drupal/http_client_manager": "^2.4",
"drupal/ldap": "4.x-dev#958f3aa79902bb9bb0cd62431b2ac9c012e292c1",
"drupal/site_settings": "^1.19",
"drush/drush": "^10"
},
Provide a stable release for Authorization with the correct commits included in the stable release, I'm not sure of other project specific approaches could fix the problem because ldap_authorization depends on authorization in the module info.yml and composer auto-installs the stable version with the current module dependencies configuartion in info.yml.
Comments
Comment #2
grahlThanks for the feedback, created an authorization release.
FYI: We are only depending generally on 1.x with "drupal/authorization": "^1.0", so the following should suffice in the root composer.json and it should not be necessary to use "as" version.
"drupal/authorization": "1.x-dev#6fbcf03c035a2c4ffcad6978991f6510f1407f48"