Provide a way to invalidate the cache without ignoring it completely

Open
#30 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
azure, r

Research direction

Start by tracing the package's authentication and cache flow to find where cached identities bypass authentication. Define how callers can invalidate that cache, then verify that a second logged-in identity reaches the account chooser instead of reusing cached credentials.

Written by the indexing model from the issue text.

Description

enhancement

Eg if there are 2 identities logged in, need to be able to force authn to occur (bring up account chooser screen) rather than simply loading from the cache.

Dominant language
R
Stars
48
Forks
23
Avg merge
4h 2m
Merged PRs (30d)
3

Contributor guide

Open the contributing guide

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 Azure/AzureAuth

All issues in Azure/AzureAuth

Similar issues

More R issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.