In menu.py

code

def add_category(self, category, icon="", label="", parent_category=""):
    label = label or category
    if parent_category == "":
        self.menu.append(MenuItem(name=category, icon=icon, label=label))
    else:
        self.find(category).childs.append(MenuItem(name=category, icon=icon, label=label))

In the last line , the 'self.find(category)...' should be '

Thanks for the new release. However I've noticed that all the changes to the documentation included in 0.5.0 aren't yet visible on the website. In particular I'm thinking about the custom test_client, which is documented here in the repo but not here on th

If using a custom authentication token model, the related_name cannot be auth_token or that will clash with the default token model related name and the django project will fail to start.

The RegisterView returns an authentication token using user.auth_token. Since the related name for a custom token model had to be changed, user.auth_token does not actually exist.

As a workaround a

Describe the feature

Ideally the documentation should mention all the datastore models required by the OpenID Connect flows. The current documentation has this section for OAuth2.0 (https://oauthlib.readthedocs.io/en/latest/oauth2/server.html#create-your-datastore-models) but it is missing for OIDC.

After a lot of wrangling - I needed to uuid, token and username to make a successful request and receive the 204 response. Please update the documentation to include the uuid.

Many thanks.

Hi,

In order to be able to use this in my Django Project, I need to be able to use the default Django decorator '@login_required()', which will redirect a user to a 'LOGIN_URL', while providing GET parameter 'next=/page-we-came-from/' after a successfull login has been performed. One the login has been performed, and the redirection to the page we came from has succeeded, the system should see t

It might be useful to have a generic system for documenting anything within PrivacyIDEA. However that is a rather large undertaking.

See: #1814

We could have a table for documentation and then add links in this table where it links to.
But the questions would be

• where display the documentation
• to whom display the documention?
  • for users?
  • for admins?

Hi, I followed the example site and managed to get the "secret" page working with 2FA setup on my website.

However, to protect the admin site, I found this ReadTheDocs article, but it doesn't seem to work. Is this procedure still the current way to make 2FA work on the admin site ?
Using this, when I go to t

According to the Instagram announcement:

UPDATE: Starting October 15, 2019, new client registration and permission review on Instagram API platform are discontinued in favor of the Instagram Basic Display API.

Need to refactor instagram backend provider, because now its not a working.

instagram backend provider use https://api.instagram.com/v1/users/self for get user data, but now i

Link : https://django-graphql-jwt.domake.io/en/latest/authentication.html#delete-cookies
Section : Delete Cookies
Wrong : # Long running refresh tokens
delete_refresh_token_cookie =
graphql_jwt.refresh_token.DeleteRefreshTokenCookie.Field()

Right : # Long running refresh tokens
delete_refresh_token_cookie =
graphql_jwt.DeleteRefreshTokenCookie.Field()

Add a source map to the doc generation process so that reference docs can link directly into source files for each function/constant/etc.

It will be useful to have more recipies of how to use various functionalities of the library.
This would be the place to suggest possible use cases and do my best to get provide a nice clean recipe for them.

• SteamClient login
• Bulding a simple web api
• Setup and use for SteamAuthenticator
• WebAuth login and use (the docs have one)
• More complex example of various St

If you override PASSWORDLESS_USER_MOBILE_FIELD_NAME from the mobile default, the API serializer is not aware and will fail on validate.

https://github.com/aaronn/django-rest-framework-passwordless/blob/dcf520fc29d7a2af2d366b80e5af0f7753c8ab20/drfpasswordless/serializers.py#L54

The serializer should use PASSWORDLESS_USER_MOBILE_FIELD_NAME for:

• querying against User model
• request p

Django doesn't guarantee a consistent ordering of models without an
explicit default ordering.

https://github.com/juanifioren/django-oidc-provider/blob/f0daed07b2ac7608565b80d4c80ccf04d8c416a8/oidc_provider/lib/utils/token.py#L158

Rotating RSA keys requires a consistent ordering, because the first key in the set of keys is always used for signing. Should we add a default ordering?

See ht

Reading the Sanic JWT docs, although override_scope_validator is mentioned in Initialization and it mentions See Scopes for more information., override_scope_validator seems to be missing in Scopes.

This should be done after #48 will be done.
From #48:

I guess the initial solution could be leaving the name user_id but allow the user identification field to be changed, and then make the change user_id -> user in next major version (0.5.0?, 1.0.0?). Probably user_id should be deprecated first, and then removed altogether.

IMPORTANT: please remember to provide backward compatibility for th

Hello
Docs about sqlalchemy is not accessible , can you provide me some example how to set up sql alchemy backends for postgres ?
Thx