idp-pw-api

idp-pw-api is a backend REST API for managing user passwords in a self-hosted SAML (Security Assertion Markup Language) Identity Provider.

  • Security
  • Tools & Utilities
idp-pw-api is a backend REST API for managing user passwords in a self-hosted SAML (Security Assertion Markup Language) Identity Provider. It exposes endpoints that let end users securely reset or change their login credentials, and it is aimed at homelabbers who run their own SAML-based identity provider and want a lightweight, self-service password management service instead of a full authentication portal.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

56/100 Fair

Maintained
100last commit 4 days ago
Popular
102 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

GitHub stars
2
Open issues
0
Last commit
2026-11-17
Latest release
10.0.6
License
MIT
Activity
rising

Checked yesterday - source: GitHub (silinternational/idp-pw-api)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Add each app you want to log into In config/samlidp.php, add each Service Provider (the app you are signing into) with its login URL, logout URL, and certificate file. Without this, the identity provider does not know where to send users or which apps are allowed, so sign-on fails. source
  • Point SAML to your key and cert files Set the certificate and private key settings, such as SAMLIDP_CERT and SAMLIDP_KEY, to where your SAML key files are stored, and keep those files private. If they are missing, signed logins break; if they are shared, someone could impersonate your identity provider. source
  • Publish the SAML config first Before changing settings, run the install steps that publish the SAML configuration, views, and migrations. That creates the files you need to edit, and without them there is nowhere to enter your SAML setup. source
  • Set up with Docker Compose Run the stack with Docker and Docker Compose: clone the repo, copy local.env.dist to local.env and edit the values, then set the DOCKER_UIDGID (uid:gid) and COMPOSER_CONFIG_FILE (full path to composer config.json) environment variables before starting the containers. source

Fetched 48 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How do I create the local environment file for idp-pw-api?

Copy local.env.dist to local.env and update the values before running the stack.

How do I make the example local API host work?

Add an entry in /etc/hosts that maps idp-pw-api.local to 127.0.0.1.

Why does the setup require DOCKER_UIDGID?

Set it to your uid:gid so some containers run as you and can write to your host filesystem with the file permissions owned by you.

Which Makefile targets are used to start and remove the idp-pw-api containers?

Run make start to get the API server online and make clean to remove all containers.

Answers sourced from github.com

Community

Collected 48 days ago - public community threads