Skip to content

Commit e31ac5a

Browse files
final changes
1 parent d07892d commit e31ac5a

File tree

3 files changed

+65
-6
lines changed

3 files changed

+65
-6
lines changed

api-reference/inference-api/authentication.mdx

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -130,3 +130,11 @@ response = openai_client.chat.completions.create(
130130
</Tabs>
131131

132132
Read more [here](/integrations/llms/openai).
133+
134+
135+
### JWT Token Authentication
136+
Portkey supports JWT-based authentication in addition to API Key authentication. Clients can authenticate API requests using a JWT token, which is validated against a configured JWKS (JSON Web Key Set).
137+
138+
<Card title="JWT Token Authentication" href="/product/enterprise-offering/org-management/jwt">
139+
You can also authenticate Portkey using JWT Tokens. Learn more here
140+
</Card>

docs.json

Lines changed: 46 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -334,7 +334,8 @@
334334
"integrations/guardrails/pangea",
335335
"integrations/guardrails/patronus-ai",
336336
"integrations/guardrails/pillar",
337-
"integrations/guardrails/prompt-security"
337+
"integrations/guardrails/prompt-security",
338+
"integrations/guardrails/bring-your-own-guardrails"
338339
]
339340
},
340341
{
@@ -2248,6 +2249,50 @@
22482249
{
22492250
"source": "/api-reference/inference-api/sdks/c-sharp",
22502251
"destination": "/api-reference/sdk/c-sharp"
2252+
},
2253+
{
2254+
"source": "product/guardrails/aporia",
2255+
"destination": "integrations/guardrails/aporia"
2256+
},
2257+
{
2258+
"source": "product/guardrails/acuvity",
2259+
"destination": "integrations/guardrails/acuvity"
2260+
},
2261+
{
2262+
"source": "product/guardrails/azure-guardrails",
2263+
"destination": "integrations/guardrails/azure-guardrails"
2264+
},
2265+
{
2266+
"source": "product/guardrails/bedrock-guardrails",
2267+
"destination": "integrations/guardrails/bedrock-guardrails"
2268+
},
2269+
{
2270+
"source": "product/guardrails/lasso",
2271+
"destination": "integrations/guardrails/lasso"
2272+
},
2273+
{
2274+
"source": "product/guardrails/mistral",
2275+
"destination": "integrations/guardrails/mistral"
2276+
},
2277+
{
2278+
"source": "product/guardrails/pangea",
2279+
"destination": "integrations/guardrails/pangea"
2280+
},
2281+
{
2282+
"source": "product/guardrails/patronus-ai",
2283+
"destination": "integrations/guardrails/patronus-ai"
2284+
},
2285+
{
2286+
"source": "product/guardrails/pillar",
2287+
"destination": "integrations/guardrails/pillar"
2288+
},
2289+
{
2290+
"source": "product/guardrails/prompt-security",
2291+
"destination": "integrations/guardrails/prompt-security"
2292+
},
2293+
{
2294+
"source": "product/guardrails/bring-your-own-guardrails",
2295+
"destination": "integrations/guardrails/bring-your-own-guardrails"
22512296
}
22522297
],
22532298
"seo": {

product/enterprise-offering/org-management/jwt.mdx

Lines changed: 11 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,10 @@ description: Configure JWT-based authentication for your organization in Portkey
99

1010
Portkey supports JWT-based authentication in addition to API Key authentication. Clients can authenticate API requests using a JWT token, which is validated against a configured JWKS (JSON Web Key Set). This guide explains the requirements and setup process for JWT authentication in Portkey.
1111

12+
<Card href="/product/guardrails/list-of-guardrail-checks#basic-%E2%80%94-deterministic-guardrails" title="Validate JWT Token (Guardarail)">
13+
Validate your JWT Token before making a LLM request using Portkey.
14+
</Card>
15+
1216
## Configuring JWT Authentication
1317

1418
JWT authentication can be configured under **Admin Settings****Organisation****Authentication**.
@@ -17,6 +21,8 @@ JWT authentication can be configured under **Admin Settings** → **Organisation
1721
<img src="/images/product/jwt.png"></img>
1822
</Frame>
1923

24+
25+
2026
### JWKS Configuration
2127

2228
To validate JWTs, you must configure one of the following:
@@ -80,7 +86,7 @@ Once the JWT is validated, the server checks for the required **scope**. Scopes
8086
List available workspaces
8187
</ParamField>
8288
</Expandable>
83-
89+
8490
<Expandable title="Logs & Analytics">
8591
<ParamField query="logs.export" type="string">
8692
Export logs to external systems
@@ -98,7 +104,7 @@ Once the JWT is validated, the server checks for the required **scope**. Scopes
98104
Access analytics data
99105
</ParamField>
100106
</Expandable>
101-
107+
102108
<Expandable title="Configurations">
103109
<ParamField query="configs.create" type="string">
104110
Create new configurations
@@ -116,7 +122,7 @@ Once the JWT is validated, the server checks for the required **scope**. Scopes
116122
List available configurations
117123
</ParamField>
118124
</Expandable>
119-
125+
120126
<Expandable title="Virtual Keys">
121127
<ParamField query="virtual_keys.create" type="string">
122128
Create new virtual keys
@@ -140,7 +146,7 @@ Once the JWT is validated, the server checks for the required **scope**. Scopes
140146
Copy virtual keys between workspaces
141147
</ParamField>
142148
</Expandable>
143-
149+
144150
<Expandable title="Workspace Users">
145151
<ParamField query="workspace_users.create" type="string">
146152
Create new workspace users
@@ -158,7 +164,7 @@ Once the JWT is validated, the server checks for the required **scope**. Scopes
158164
List workspace users
159165
</ParamField>
160166
</Expandable>
161-
167+
162168
<Expandable title="Other">
163169
<ParamField query="prompts.render" type="string">
164170
Render prompt templates

0 commit comments

Comments
 (0)