K2 Five

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. K2 User Licensing – Auto clear users who have not accessed in over a year.

    It will be good to have a functionality in K2 that can auto clear users who has not accessed K2 in over a year.

    Currently K2 stores all the Users in K2 Identity table who have accessed K2 atleast once in life time. There are Users in the table who logged in only once and has never accessed K2 for many years. There are also users in K2 Identity table who left the Organization.

    The Identity table grows huge over the years and the K2 Audit Report shows each and every user in the Identity Table as Active User. This…

    8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Identity  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. K2 Five SYNC (AD\LDAP) - Excluding specific objects or OUs during Syncing is not possible currently

    Currently, When we add a new domain to the K2 Five Identity Sync, there is no option to Exclude specific objects or OUs. Customers with multiple domains may require this feature as there could be same ID across multiple domains. In which case, searching by User Id or the First Name/Last Name appears to have multiple results for the same user which makes it difficult to pick the right account in the result set.

    31 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Identity  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. SyncEngine - Ability to handle duplicate Group Names

    Current Identity and New SyncEngine cannot cache duplicate groups in the Identity Schema, all though AAD allows creation of duplicates (Not true duplicate as ObjectID differs). Identity enforces uniqueness, Identity has a rule that ensures FQN and Type composite values are enforced to ensure unique records. Due to this the group will have the same FQN.

    This idea is to handle duplicates in cases like this where Name / DisplayName is the same but the underlying ObjectID differs.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Identity  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?

Feedback and Knowledge Base