Enum for scope

[EricGaim]

Hello!

I have been working with this sdk to try helping a colleague have to do a little less menial work but I am still a novice so I'm having an issue. I was able to get everything working with static token but having to use enums for scope is giving me a little bit of an issue. I can't seem to find a way to get any good answers on the right way to do it. May I have some help on this please?

Kind regards,
Eric Wingård

[richardrandak]

Hello Eric. What exactly is the problem?
The scopes are used only for the new auth workflow. The static token workflow does not use them.

Can you please describe your situation with a little more details?

[richardrandak]

By Oauth1 you mean the old workflow with non-expirable token right?

1. The deadline was moved to January 9th - https://developer.fortnox.se/blog/delay-with-oauth2/
2. All tokens should still continue to work, but you won't be able to activate a new one. So, basically, you won't be able to get any new customers for that solution.

I can not guarantee you anything anymore, but this is what I heard from Fortnox support and how I understand it :)

[EricGaim]

Yes exacly, static token. Since this solution is only for us to automate our own process and are not looking to sell this to any customers it should be fine with static token, right?

[richardrandak]

Yes, it should be fine! You already have a static token right?

One thing to note here is that even though the deadline is not here yet, in my experience, new apps created after September have the old workflow disabled already, more specifically, they do not appear in the integrations list so the API key (auth code) can't be generated. It was not documented anywhere, but I had this problem.

[EricGaim]

I believe my app was created in oktober or november originally but I have a static token for it so I'm assuming it will be fine and won't suddenly stop working in January right? The problem right now is that the app is only being used in our test environment so I might have to try and get a static token working straight away on the production version.

[richardrandak]

Yes, please try it. In my situation, I could find the app by clientid for several minutes, but then it disappeared from the list, so later I could not reproduce it. So maybe you managed to get the token in that weird "window", which seems like a bug :D Let me know how is it in your situation.