Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Remove obsolete / insecure OAuth2 flows from this spec

Open
  • Is something wrong?
#27 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Stale
Domain
authentication, documentation, security

Research direction

Open the linked “Obtaining authentication information” section and locate the two listed OAuth2 flows. Done means both obsolete flows are removed from the specification and no longer appear in that section.

Written by the indexing model from the issue text.

Description

Here, we're listing two flows: https://github.com/buildingSMART/foundation-API#221-obtaining-authentication-information

  • implicit_grant, which has been effectively deprecated, or at least it's usage is heavily discouraged
  • resource_owner_password_credentials_grant, which never really was considered secure in scenarios where you did not control all services involved

This was brought up in the meeting today, and we should just remove it from the spec completely.

Dominant language
No language data
Stars
39
Forks
9
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from buildingSMART/foundation-API

All issues in buildingSMART/foundation-API

Similar issues

More Security issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.