enhance: blog: add  for list view

saviynt · Dec 9, 2024 · 06f2cf8 · 06f2cf8
1 parent eca028c
commit 06f2cf8
Show file tree

Hide file tree

Showing 2 changed files with 8 additions and 4 deletions.
diff --git a/blog/2024-04-12-new-phase-community-connectors.mdx b/blog/2024-04-12-new-phase-community-connectors.mdx
@@ -6,15 +6,17 @@ tags: [community-connectors]
 ---
 import GitHubComments from '@site/src/components/Github/Comments';
 
- ## **[Community Connector @ Developer Portal](https://saviynt.github.io/developer-portal/community/connectors)**
+ ## [Community Connector @ Developer Portal](https://saviynt.github.io/developer-portal/community/connectors)
 
 In the ever-evolving landscape of software development and integration, the ability to collaborate, innovate, and swiftly adapt to changes is paramount. This is why we have made a significant shift in how we handle our community connectors: moving them from traditional forums and exchange sites to our newly established Developer Portal, which leverages Git as its backend. This transition marks a strategic shift  in our approach to managing and disseminating these crucial resources. Here, we’ll explore the motivations behind this move and the benefits it brings to developers and system integrators.
 
-### **Limitations of Forums and Exchange Sites**
+<!-- truncate -->
+
+### Limitations of Forums and Exchange Sites
 
 Previously, our community connectors were housed on forums and exchange sites. While these platforms provided a basic framework for sharing and downloading connectors, they had notable limitations. Users could browse available connectors and download them, but interaction was largely restricted to commenting within forums. This setup offered no facility for direct modification or enhancement of the connectors, which stifled collaboration and the organic growth of our tools.
 
-### **Why Move to a Developer Portal with Git?**
+### Why Move to a Developer Portal with Git?
 
 Our decision to transition to a Developer Portal using Git is rooted in our commitment to enhancing developer engagement and promoting a more vibrant ecosystem of tools. Git, a widely used version control system, allows for robust collaboration and version control, making it an ideal backbone for our Developer Portal. Here are the key reasons and benefits of this move:
 
@@ -34,7 +36,7 @@ One of the significant advantages of using Git is the transparency it brings to
 
 Our Developer Portal is designed with discoverability in mind. Developers can easily search for connectors, view documentation, and download the tools they need. The Git backend supports version control and release management, which means that users can access both current and previous versions of connectors, enhancing compatibility and testing across different environments.
 
-### **Looking Ahead**
+### Looking Ahead
 
 This transition to a Developer Portal with a Git backend is more than just a change of platform; it is a fundamental shift in how we engage with and support our developer community. It encourages a more active, collaborative, and transparent approach to managing the development and utilization of community connectors.
 

diff --git a/blog/2024-12-08-introducing-oauth2-token-exchange-with-oidc.mdx b/blog/2024-12-08-introducing-oauth2-token-exchange-with-oidc.mdx
@@ -13,6 +13,8 @@ OAuth 2.0 and OpenID Connect are the most popular and important security protoco
 
 Specifically, this is implemented using industry standards OAuth 2.0 Token Exchange flow ([IETF RFC-8693](https://datatracker.ietf.org/doc/html/rfc8693)) and the associated OAuth 2.0 Token Introspection API ([IETF RFC-7662](https://datatracker.ietf.org/doc/html/rfc7662)). The token exchange can be performed submitting an IdP OAuth 2.0 access token or an IdP OIDC ID token to Saviynt Identity Cloud, which will exchange it for a Saviynt OAuth 2.0 access token. Read more below for an overview and in our [documentation for "Configuring OAuth 2.0 Token Exchange Authentication"](https://docs.saviyntcloud.com/bundle/EIC-Admin-v24x/page/Content/Chapter06-EIC-Configurations/OAuth-Token-Exchange.htm).
 
+<!-- truncate -->
+
 ## How it Works
 
 At a high level, OAuth 2.0 Token Exchange works with applications requesting a Saviynt Identity Cloud API Access Token by presenting and IdP issued token, which can be an OAuth 2.0 access token or an OIDC ID token, both issued by the IdP. There are 3 major parts to such an integration, described below.