[bug]: Try to set the Bearer token automatically into the environment variables.

[matheuscararodojunior]

Describe the bug
Hi, I'm a fullstack developer, and I'm transitioning my development team to use Firecamp because Postman is extremely expensive.
However, I'm facing an issue: on my machine (MacBook M2 Silicon, 16GB RAM), after performing login, the Bearer token is not being automatically added to the environment like it happens in Postman.
In Postman, after logging in, I set the Bearer token into the environment variables without any problem, but in Firecamp this is not happening at all.

Here is an example of the tests I'm running:

fc.test("Successful POST request", () => {
    fc.expect(fc.response.code).to.be.oneOf([201, 202]);
});

fc.test("Test", () => {
    fc.collectionVariables.set('itemId', 14);
    fc.expect(fc.response.code).to.be.oneOf([201, 202]);
});

fc.test("Response time is less than 200ms", () => {
    fc.expect(fc.response.responseTime).to.be.below(200);
});

fc.collectionVariables.set("authorization", "variable_value");

I've tried several approaches but I still couldn't solve this.

Please help me!

---

To Reproduce
Steps to reproduce the behavior:

1. Perform login through Firecamp.
2. Try to set the Bearer token automatically into the environment variables.
3. Execute requests that require Authorization header.

Expected behavior
After login, the Bearer token should be available in the environment (like in Postman), allowing the requests to be authenticated automatically.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: macOS
• Device: MacBook Pro M2 Silicon, 16GB RAM
• Firecamp version: 3.3.0 Beta

Additional context
I am moving my whole development team to Firecamp due to Postman's pricing. Solving this Bearer token issue is critical for us to continue the migration.

[AnuGuin]

Hey Matheu! Just wanted to know as this issue has not been addressed for a while are you still using Firecamp and actively migrating to it? If yes can you please elaborate which encrypting framework you are using. I will be glad to help in this issue also might get a valuable learning through this issue/bug-fix