Sign in to pgEdge Starfleet in the browser instead of with API client credentials

未关闭
#10,746 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 2 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
postgresql, python

调研方向

Start by reading the Deploy Cloud Instance wizard issue #10499 and the existing Azure sign-in flow in pgAdmin, then trace the pgEdge Starfleet option that currently accepts an API client ID and secret. The change should support browser sign-in using a short code, tenant selection for users in multiple tenants, and continued use of API client credentials as an alternative.

由索引模型根据 Issue 内容生成。

描述

The pgEdge Starfleet option in the Deploy Cloud Instance wizard (#10499) asks for an API client ID and secret. To get those, a user has to open the pgEdge Starfleet console, create an API client, copy both values into pgAdmin, and then remember to revoke the client when they no longer need it. That is a lot of setup for someone who already has a pgEdge Starfleet login and just wants to create a database.

pgAdmin should let the user sign in with their existing pgEdge Starfleet account in the browser, by entering a short code that the wizard shows them, much as the Azure option already does. A user who belongs to more than one pgEdge Starfleet tenant should be able to choose which one to use. API client credentials should stay available as an alternative for anyone who prefers them.

主要语言
Python
星标
3.9k
派生
918
平均合并
2 天 12 小时
30 天内合并 PR
35

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

pgadmin-org/pgadmin4 的其他 Issue

查看 pgadmin-org/pgadmin4 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。