starred/hoppscotch

Fork 0

mirror of https://github.com/hoppscotch/hoppscotch.git synced 2026-04-26 01:06:00 +03:00

[GH-ISSUE #4808] [bug]: Inherited Authorization from a collection is not working when using variables #1801

New issue

Closed

opened 2026-03-16 21:47:25 +03:00 by kerem · 5 comments

kerem commented

2026-03-16 21:47:25 +03:00

Owner

Originally created by @furai on GitHub (Mar 4, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4808

Originally assigned to: @nivedin on GitHub.

Is there an existing issue for this?

I have searched the existing issues

Current behavior

When using environment variables that get injected into properties in collection for authorization of whole set of different request I'm getting errors that the request was unauthorized.

It used to work before today's update.

Possibly related to: #4804

Steps to reproduce

!. Go to hoppscotch.io
2. Create environment with variables
3. Create collection with authorization in properties using environment variables
4. Add some requests that inherit that authorization

Environment

Production

Version

Cloud

Originally created by @furai on GitHub (Mar 4, 2025). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4808 Originally assigned to: @nivedin on GitHub. ### Is there an existing issue for this? - [x] I have searched the existing issues ### Current behavior When using environment variables that get injected into properties in collection for authorization of whole set of different request I'm getting errors that the request was unauthorized. It used to work before today's update. Possibly related to: #4804 ### Steps to reproduce !. Go to hoppscotch.io 2. Create environment with variables 3. Create collection with authorization in properties using environment variables 4. Add some requests that inherit that authorization ### Environment Production ### Version Cloud

kerem

2026-03-16 21:47:25 +03:00

closed this issue
added the
bug

need testing
labels

kerem commented

2026-03-16 21:47:41 +03:00

Author

Owner

@endrik-exe commented on GitHub (Mar 4, 2025):

Happens here also.

Checked the network tab in the devtools and found that the <<variable>> in the request header is not replaced with actual value

@endrik-exe commented on GitHub (Mar 4, 2025): Happens here also. Checked the network tab in the devtools and found that the `<<variable>>` in the request header is not replaced with actual value

kerem commented

2026-03-16 21:47:46 +03:00

Author

Owner

@murad-apex commented on GitHub (Mar 5, 2025):

Happens here also.

Checked the network tab in the devtools and found that the <<variable>> in the request header is not replaced with actual value

I have also same issue

@murad-apex commented on GitHub (Mar 5, 2025): > Happens here also. > > Checked the network tab in the devtools and found that the `<<variable>>` in the request header is not replaced with actual value I have also same issue

kerem commented

2026-03-16 21:47:51 +03:00

Author

Owner

@Macek007 commented on GitHub (Mar 6, 2025):

Same issue - I am adding screenshot for better description

@Macek007 commented on GitHub (Mar 6, 2025): Same issue - I am adding screenshot for better description ![Image](https://github.com/user-attachments/assets/73a23065-65ee-469e-817b-af84026f997e)

kerem commented

2026-03-16 21:47:56 +03:00

Author

Owner

@jamesgeorge007 commented on GitHub (Mar 7, 2025):

Hi, this is fixed in the latest release. Please let us know if the issue persists.

@jamesgeorge007 commented on GitHub (Mar 7, 2025): Hi, this is fixed in the latest release. Please let us know if the issue persists.

kerem commented

2026-03-16 21:48:01 +03:00

Author

Owner

@furai commented on GitHub (Mar 10, 2025):

Seems to be fixed on my end, thank you!

@furai commented on GitHub (Mar 10, 2025): Seems to be fixed on my end, thank you!