Streaming API - with and without authentication | Community
Skip to main content
Michael_Soprano
Level 10
July 4, 2025
Solved

Streaming API - with and without authentication

  • July 4, 2025
  • 2 replies
  • 417 views

What is the difference when it comes to workflow with authentication and without?

WIth we needs to generate beforehand token?

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by somen-sarkar

Workflow with authentication is necessary when dealing with sensitive data or when you need to enforce access control. It provides security and ensures that only authorized users can interact with the system.


Without authentication is suitable for public data or services where security is not a concern. It simplifies access but lacks the protections provided by authentication.

 

Authentication related attributes need to be passed with the api request. Pls check the below article.
API authentication

2 replies

somen-sarkar
Community Advisor
somen-sarkarCommunity AdvisorAccepted solution
Community Advisor
July 4, 2025

Workflow with authentication is necessary when dealing with sensitive data or when you need to enforce access control. It provides security and ensures that only authorized users can interact with the system.


Without authentication is suitable for public data or services where security is not a concern. It simplifies access but lacks the protections provided by authentication.

 

Authentication related attributes need to be passed with the api request. Pls check the below article.
API authentication

KumarRishii
Level 5
July 4, 2025

With Authentication (ON):

Requires Adobe IMS access token (JWT or OAuth).
Secure and recommended for production.
Token sent via Authorization header.
Ensures controlled and auditable access.

Without Authentication (OFF):

No token needed; simpler setup.
Suitable for development or testing only.
Not secure — anyone with the endpoint can push data.