Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • fusiondirectory fusiondirectory
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 33
    • Issues 33
    • List
    • Boards
    • Service Desk
    • Milestones
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • fusiondirectoryfusiondirectory
  • fusiondirectoryfusiondirectory
  • Issues
  • #5863
Closed
Open
Issue created Jun 20, 2018 by bmortier@bmortierMaintainer

adapt fusiondirectory-setup to migrate the supannTypeEntite attribute to contain {SUPANN} prefix

Description

It seems that prior to 1.3 FD was storing supannTypeEntite value without the {SUPANN} prefix

FusionDirectory Version

1.2.1

Plugin with the defect

Supann

Steps to Reproduce

  1. Save a Supann entite
  2. Look at the LDAP value for supannTypeEntite

Expected behavior:

{SUPANN} prefixed value

Actual behavior:

Value without prefix

Additional Information

This also mean that data migration will be needed from 1.2.1 to 1.3 (or 1.2.2 if we fix it in this version) for people with existing supann entite objects.

Edited Aug 07, 2018 by bmortier
Assignee
Assign to
Time tracking