Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request]: Loading match from url limitations #1012

Closed
2 tasks done
LowArte opened this issue Apr 10, 2023 · 4 comments
Closed
2 tasks done

[Feature Request]: Loading match from url limitations #1012

LowArte opened this issue Apr 10, 2023 · 4 comments

Comments

@LowArte
Copy link

LowArte commented Apr 10, 2023

Prereleases & Documentation

Get5 Version

0.14.1

The Feature

For creating matches right now i'm using get5_loadmatch_url, but i have a very long bearer token and url with guid's.
As i know commands have 255 character limitations for commands, how can i get around this limitation ?

@nickdnk
Copy link
Collaborator

nickdnk commented Apr 10, 2023

You cannot get around this, unfortunately. Make your auth token and URL shorter.

@LowArte
Copy link
Author

LowArte commented Apr 10, 2023

Thanks, but i have an idea. If you can create login in external systems it can be fixable. For example in get5_loadmatch_url instead of token argument, set 2 new parameters username and password for external system. And also add configuration parameter or another argument "external auth url"

@nickdnk
Copy link
Collaborator

nickdnk commented Apr 10, 2023

Thanks, but i have an idea. If you can create login in external systems it can be fixable. For example in get5_loadmatch_url instead of token argument, set 2 new parameters username and password for external system. And also add configuration parameter or another argument "external auth url"

If you want to use username and password, just provide that as the header arguments? You don't have to use a JWT. For HTTP basic auth, it would be this: Authorization: Basic <credentials>, where credentials is the Base64 encoding of username and password joined by a single colon.

I don't understand the second part.

Regardless, I'm no longer adding features to Get5, so I won't be doing this.

@LowArte
Copy link
Author

LowArte commented Apr 10, 2023

I undestand, thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants