feat(jans-cli-tui): create ACR screen on TUI

yuriyz commented 6 months ago

Description

TUI "ACR" screen should have clear sections: 1) Built-in For now it's just: simple_password_auth 2) Script acrs all script names listed here 3) Aliases Mappings between alias and technical name acr_values=myOTP -> acr_values=org.gluu.agama.otp.main 4) Agama flows acr_values=agama_org.gluu.agama.otp.main

https://chat.gluu.org/group/service_auth_server?msg=Dca2335PvjKNsFN8b

Relevant documents that might need updates

Note: The developer needs to add to this list based on the complete understanding of the feature and its implementation

Add a new document under config guide with screens and relevant explanation. Also, if the same is possible via CLI, then add those command too in the same document.

Test cases and code coverage

[ ] Write unit test to cover added/changed code
[ ] Update integration tests to cover added/changed code

Document the changes

[ ] task for updating user guides if needed
[ ] task for updating installation and configuration guides if needed
[ ] task for updating developer documentation if needed
[ ] task for updating technical documentation if needed

yuriyz commented 6 months ago

Wait until this ticket is solved https://github.com/JanssenProject/jans/issues/8216

ossdhaval commented 6 months ago

updated the description for documentation tasks

devrimyatar commented 1 month ago

@yuriyz Should I extend the following screen for Aliases and Agama Flow

authn

nynymike commented 1 month ago

It would be nice if simple_password_auth and auth_ldap_server were configurable by the admin.

devrimyatar commented 1 month ago

It would be nice if simple_password_auth and auth_ldap_server were configurable by the admin.

Yes they are

yuriyz commented 1 month ago

@yuriyz Should I extend the following screen for Aliases and Agama Flow

@devrimyatar yes

duttarnab commented 1 month ago

Hi @yuriyz @devrimyatar @pujavs

Agama flows can be obtained from API (config-api). We need the fields list to be shown on screen /jans-config-api/api/v1/agama-deployment
For Aliases I think we need API. We also need the fields list to be shown on screen.

yuriyz commented 1 month ago

Aliases are part of AS config. So this should already work.

{
  ...
  "acrMappings": {
    "acr_alias1": "basic",
    "acr_alias2": "otp" 
  }
  ...
}

@duttarnab thanks for sharing info for Agama flows. I guess it was missing piece for @devrimyatar

devrimyatar commented 1 month ago

Aliases are part of AS config. So this should already work.
{
  ...
  "acrMappings": {
    "acr_alias1": "basic",
    "acr_alias2": "otp" 
  }
  ...
}
@duttarnab thanks for sharing info for Agama flows. I guess it was missing piece for @devrimyatar

@yuriyz I imeplemented Aliases section

duttarnab commented 1 month ago

Hi @yuriyz my understanding is, for Agama Flows we need to show all the added Agama projects on the auth server. We already have a screen for this, we just need to shift this screen under a separate tab under Authn menu. Kindly let us know if this understanding is incorrect.

yuriyz commented 1 month ago

Right, idea is to show it on TUI as well.

JanssenProject / jans