You are viewing a single comment's thread from:
RE: Need help with upload API auth system. Any ideas?
As you stated we do not ask for posting keys thus maybe the best option is solution #2 and I would assume users that wish to use our service would understand.
The technical is by far over my head so I can only go off what information you have provided. If it will work for our existing 2 sign in methods with the uploader I see no reason not to do it for the mean time while working on further possible solutions for posting keys or just continuing to support just the two auth systems. Sounds like some serious development of the main components is required to make every option viable, not sure how challenging that will be?
Posted using Partiko iOS
Solution 2 will break support for posting key login on d.tube since there's no way that you can generate access token for those. Remember that the API will be called from our website, d.tube and potentially other websites as well.
If we decide to depreciate SteemConnect altogether then solution 1 will work.
Could you not have posting key just doable the process’s used for alternative upload servers? Have it runs as it does now with the added benefit of those using Steemconnect or Keychain able to select destination?
I do agree keeping posting key available is essential.
Posted using Partiko iOS
The whole idea is to allow uploading to our servers from their interface, not redirecting to another domain, regardless of auth method.
Another solution would be combining multiples. That could be options of either submitting SteemConnect access token or using a one-time
upload_token. The API may accept either inputs.Right now an investigation is being carried out to find out how our users are logging into our uploader. Let's see how it turns out here after 7 days.
Sounds like a plan to me 🤙
Posted using Partiko iOS