Closed aitorcelaya closed 3 years ago
As of v1.1.0, the certfile
attribute is now depricated, as Omejdn now chooses its own filenames. It will accept new certificates if you change it to import_certfile
.
We should really start to write release notes...
Regarding the user_selfservice
option:
Omejdn, while it can be used as as a DAPS, is actually an OAuth2 compatible Authorization Server. Hence it does support many more options than necessary here.
The provided DAPS example configuration disables many of these functionalities.
Did that fix the issue?
Closing this issue due to a lack of further information. Feel free to reopen it should the problem persist.
I have installed the latest DAPS version as I have seen changes in the last couple of weeks and I am having issues obtaining a DAT through the "create_test_token.rb" script. I have copied the same changes I performed in a previous DAPS version, but it is not working as expected.
The copy I currently have was called v0.0.2 when this repo showed the version. The working version was downloaded in the beginning of the month and the new version was downloaded last week as of this post.
I have taken screenshots below regarding the working version in the LEFT and the non-working version on the RIGHT.
config/clients.yml:
config/omejdn.yml. The DAPS in the right also has "user_backend". It is not shown here because it was not altered in any way. It also has "user_selfservice":
keys/:
scripts:
scripts/create_test_token.rb:
Response from the "old" DAPS:
Response from the "new" DAPS:
Is there anything I may be missing? It was not working, so I copied the old setup and it still will not work.
Is it an option to keep having versions as to avoid this in the future? Instead of "old" vs "new", have a v0.0.2 vs v0.0.3.