From f7749ae07fe13479bf92c48c4dbbfe5d3a63c82f Mon Sep 17 00:00:00 2001
From: Himanshu Mishra <himanshu@orkohunter.net>
Date: Mon, 12 Dec 2022 11:38:23 +0530
Subject: [PATCH] update changeset with example and change minor to patch (#7)

Signed-off-by: Himanshu Mishra <himanshu@orkohunter.net>

Signed-off-by: Himanshu Mishra <himanshu@orkohunter.net>
---
 .changeset/violet-dots-relate.md | 29 +++++++++++++++++++++++++++--
 1 file changed, 27 insertions(+), 2 deletions(-)

diff --git a/.changeset/violet-dots-relate.md b/.changeset/violet-dots-relate.md
index 3b63129337..bc6b75caf9 100644
--- a/.changeset/violet-dots-relate.md
+++ b/.changeset/violet-dots-relate.md
@@ -1,5 +1,30 @@
 ---
-'@backstage/core-components': minor
+'@backstage/core-components': patch
 ---
 
-Added option to pass additional headers in ProxiedSignInPage
+Added option to pass additional headers to `<ProxiedSignInPage />`
+
+The <ProxiedSignInPage /> supports signing into Backstage with a Sign Page coming from an external provider e.g. Google IAP, AWS ALB, etc. The component makes requests to a single endpoint `/refresh` on the auth backend to fetch the logged in user session.
+
+If the provider in auth backend expects additional headers such as `x-provider-token`, there is now a way to configure that in `ProxiedSignInPage` using the optional `getHeaders` prop.
+
+Example -
+
+```tsx
+const app = createApp({
+  // ...
+  components: {
+    SignInPage: props => (
+      <ProxiedSignInPage
+        {...props}
+        provider="my-custom-provider"
+        getHeaders={async () => {
+          const someValue = await someFn();
+          return { 'x-some-key': someValue };
+        }}
+      />
+    ),
+  },
+  // ...
+});
+```