hackforla / hackforla/knowledgebase

Sychronize users between people depot and kb

Ouverte
#75 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub
complexity: medium draft feature: table: user milestone: missing role: back end dev size: 2pt
Langage dominant
Python
Étoiles
2
Forks
5
Métriques de merge des PR
Aucune PR mergée en 30 j

Description

### Blockers/Dependencies
None

### Overview
REPLACE THIS TEXT -Text here that clearly states the purpose of this issue in 2 sentences or less.

### Action Items
- [ ] User synch
- [ ] If PEOPLE_DEPOT_URL is defined in kb when user logs in, confirm PEOPLE_DEPOT URL works. If it doesn't work, error message and prevent creation of user.
- [ ] Prevent creation of user in KB ifcannot create in PD
- [ ] Manual tests
- [ ] Sign up for account in kb.
- From sqlite browser
- verify account is created in PD
- verify account is created in BD
- Compare user account in PD and KB
- compare to Cognito
- Log in to kb using new account - verify message no authorization
- Log in to pd using new account- verify message no authorization
- Test API call from kb to pd
- Verify call people depot URL indicates authenticated but not authorized
- Set is_staff to true in PD
- Verify call people depot urlworks
- Document manual tests
- [ ] Sign up for account in pd.
- From sqlite browser
- verify account is created in PD
- sign in to using KB cognito account
- verify account is created in KB
- Compare user account in PD and KB
- compare to Cognito
- Log in to kb using new account - verify message no authorization
- Log in to pd using new account- verify message no authorization
- Test API call from kb to pd
- Verify call people depot URL indicates authenticated but not authorized
- Set is_staff to true in PD
- Verify call people depot urlworks
- Document manual tests
- [ ] Implement and test updating user in kb, see gets changed in pd
- [ ] Decide on strategy on
- what to do if pd is down and new account is created - how to eventually resynch

REPLACE THIS TEXT -If the issue has already been researched, and the course of action is clear, this will describe the steps. However, if the steps can be divided into tasks for more than one person, we recommend dividing it up into separate issues, or assigning it as a pair programming task.

### How to Manually Verify
REPLACE THIS TEXT - Describe how to manually verify either through UI or executing the code and inspecting.

### Automated Tests
Any automated tests?

### Resources/Instructions
REPLACE THIS TEXT -If there is a website which has documentation that helps with this issue provide the link(s) here.

Guide de contribution

Ouvrir le guide de contribution

Piste de recherche

Commencez par suivre les parcours d’inscription et de connexion ainsi que l’intégration de PEOPLE_DEPOT_URL ; aucun fichier source ni test automatisé n’est nommé dans l’issue. Utilisez les vérifications manuelles indiquées pour KB, People Depot et Cognito comme plan de vérification, en incluant la gestion des services indisponibles et les mises à jour des utilisateurs. La tâche est terminée lorsque le comportement de synchronisation et une stratégie de resynchronisation ont été convenus, implémentés, testés et documentés.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
python, sqlite
Domaine
api, authentication, backend, databases
Type d'issue
Fonctionnalité
Difficulté
5/5
Temps estimé
Plus d'une semaine
Activité
À l'abandon
Clarté
À clarifier
Accessibilité débutants
15/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.