forcedotcom / forcedotcom/NextGeneration-DevOpsCenter

Authentication to Production Branch Issue

Aperta
#2 5 commenti 0 reazioni 0 assegnatari Vedi su GitHub
type: awaiting-user-response
Lingua principale
Nessun dato sulla lingua
Stelle
7
Fork
1
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

Maybe hard to reproduce and might have been a "me" thing, but when I went to authorize the production org in the pipeline it Popped up a modal to login, and when I logged in on the modal it logged me into prod in that screen, but logged me out of prod on the main screen. When I went back into the environment it said it did not authenticate and I had to try again, leave the modal open and then it worked for some reason (but still logged me out on the main screen).

Also, not a bug, but a feature request. - Make pipeline building easier - I can't be the only person to use SSO in production but have to login to sandboxes with whatever my password was in production whenever it was that I had set it. Ideally, setting up a pipeline would allow you to configure environments leveraging connected apps or some other feature where the individual user who is creating the pipeline doesn't have to login to every environment in order to configure it. Long term, I would love to see a simpler way to access sandboxes in general for myself and for my users who want to test or see prototypes in various environments without having to remember which environment something was in.

Guida per i contributori

Nessuna guida per i contributori indicizzata per questo repository

Direzione di ricerca

Inizia riproducendo il flusso di autorizzazione di production-org, confrontando il login modale con la schermata principale e verificando se l’ambiente rimane autenticato. L’issue è completata quando l’autenticazione persiste in modo coerente; la richiesta di funzionalità più ampia relativa a SSO e sandbox-access richiede un ambito e una progettazione separati.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Valutazione

Ambito
authentication, devops
Tipo di issue
Bug
Difficoltà
4/5
Tempo stimato
3-5 giorni
Stato di attività
Tranquilla
Chiarezza
Da chiarire
Idoneità per principianti
25/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.