Tycho sessionid

[frostyfan109]

Modify Tycho to allow encoding arbitrary environmental variables into app pods. We now encode sessionid as ACCESS_TOKEN and grader API URL as GRADER_API_URL (if the setting in appstore is set) into pod environments.

[joshua-seals]

@frostyfan109 What is the big picture here for this augmentation, for my own understanding?

[joshua-seals]

This looked odd due to multiple runs through of 256, so I asked cGPT to optimize.

Characters to use for the token

characters = string.ascii_letters + string.digits

# Generate a token and check for uniqueness
while True:
    token = ''.join(secrets.choice(characters) for _ in range(256))
    if not UserIdentityToken.objects.filter(token=token).exists():
        return token

[frostyfan109]

well we could just use the := operator but I'm not sure what versions of python we need to support in Appstore

[frostyfan109]

@frostyfan109 What is the big picture here for this augmentation, for my own understanding?

This a change for Eduhelx so that we can embed a secret into apps so they can authenticate with appstore without embedding the cookie directly. I'm not sure this is the correct approach need to run it by a couple others.

[joshua-seals]

@frostyfan109 What is the big picture here for this augmentation, for my own understanding?

This a change for Eduhelx so that we can embed a secret into apps so they can authenticate with appstore without embedding the cookie directly. I'm not sure this is the correct approach need to run it by a couple others.

Ok that makes sense. Does this enable refreshes to the token now?

If no, may not be a big deal now, but the other potential option is having a sidecar that handles traffic for each app. The sidecar would do the session refresh and all that jazz and is easier to control (and the same) across all the differing applications we provide.
This is a "Mesh-ish" sort of capability and would also come with benefits of encryption between all endpoints if we so chose.

[frostyfan109]

@frostyfan109 What is the big picture here for this augmentation, for my own understanding?

This a change for Eduhelx so that we can embed a secret into apps so they can authenticate with appstore without embedding the cookie directly. I'm not sure this is the correct approach need to run it by a couple others.

Ok that makes sense. Does this enable refreshes to the token now?

If no, may not be a big deal now, but the other potential option is having a sidecar that handles traffic for each app. The sidecar would do the session refresh and all that jazz and is easier to control (and the same) across all the differing applications we provide. This is a "Mesh-ish" sort of capability and would also come with benefits of encryption between all endpoints if we so chose.

No refresh right now, the tokens just live for the lifetime of the app. This isn't intended to be a permanent solution, but if it does become one I like your idea.