Allow change of SAML Certificate Expiry Date

Open
#1,799 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
go
Domain
authentication

Research direction

Start by reading the certificate configuration in internal/conf/saml.go around lines 100-112, where the current validity behavior is defined. Trace how that configuration is used for SAML certificates and confirm the expected behavior for IdP validity periods. Done means a customer can set a validity period of up to 3-5 years as required by providers such as Ping Identity.

Written by the indexing model from the issue text.

Description

bug

Bug report

A customer reported that they need to set the validity period as per the best practices of their idp, in this case Ping Identity for a period of up to 3-5 years.

This isn't possible given how the certificate works now

We welcome Pull Requests to address this

Dominant language
Go
Stars
2.6k
Forks
764
Avg merge
5d 3h
Merged PRs (30d)
39

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 supabase/auth

All issues in supabase/auth

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.