Make the redirection endpoint optional

[caeies]

Hi all,

First, thanks for this promising project.

I was planning to play with Himalaya + gmail as a replacement candidate to cmdg.

I'm running under a debian 13.2 distribution, using rustup / rust installed toolchain 1.96.

I never run anything from the himalaya framework before.

According to the documentation, we can use either ~/.ortierc or ~/.config/ortie.toml. Of course, as a dummy user, I tried to create my config to ~/.config/ortie.toml. But ortie was failing to locate the config file. Short story: this is either ~/.ortierc OR ~/.config/ortie/config.toml (at least in the version installed by cargo install ortie).

Once this issue solved, I tried to get a token which fails miserably for two reasons:

• First I forget to setup the redirection URL -> failure occurs.
• My computer is running a web server: the default redirection is done on 80 -> as user -> permission denied (because port is < 1024). Why not in such conditions running (as all others tools I know doing this kind of stuff) on a random > 1024 port ? To workaround that I had to use endpoints.redirection = "http://localhost:12312"
• Once this pitfall passed (I skip all the failures, one interesting one is that initial requests were using a wrong scope, I don't known where this is coming from): the auth get was failing with no such file or directory ... After stracing the binary, I found that I should install the pass package (apt install pass) ... I don't see this at any place, so I'm probably missing something to a missing feature thing during the installation ?
• Initial retry fails with the pass binary complaining ... I made the guess that the pass init my_gpg_id was missing.
• did it and finally get the token !
• but looking at pass show output, I saw that it is stored under the ortie -> example entry instead of the my_acount_name value (aka [accounts.my_acount_name]

I know that this software is still under development, so I take the time to fill this issue :).

Best regards.

Caeies.

[soywod]

Sorry for the delay, I somehow did not receive any mail for your issue. I was busy on Himalaya new release.

• First I forget to setup the redirection URL -> failure occurs.
• My computer is running a web server: the default redirection is done on 80 -> as user -> permission denied (because port is < 1024). Why not in such conditions running (as all others tools I know doing this kind of stuff) on a random > 1024 port ? To workaround that I had to use endpoints.redirection = "http://localhost:12312"

They both go together. If the redirection URL is missing then it should take localhost by default with the first random available port. I will adjust this option, thanks for the feedback.

• After stracing the binary, I found that I should install the pass package (apt install pass) ... I don't see this at any place, so I'm probably missing something to a missing feature thing during the installation ?

Ortie does not rely on any other third party tool. Pass is used as example. I believe you reference this part from the config sample:

# Access token storage
#
storage.read.command = ["pass", "show", "ortie/example"]
storage.write.command = ["pass", "insert", "-e", "ortie/example"]

Ortie needs to store (write) and retrieve (read) the access and refresh token. But Ortie does not know how to do, this only depends on your setup. If you use pass for example, then the configuration above will work. Which keyring do you use on your system?

[soywod]

If the redirection URL is missing then it should take localhost by default with the first random available port. I will adjust this option, thanks for the feedback.

If the redirect URI is missing, it will default now to http://127.0.0.1:0, which will take the default available port. The feature is on master and will be available in the next release.

If you have any other question, feel free to reopen or to joint our Matrix room.