How to Install and Uninstall python2-flask-jwt-extended Package on openSUSE Leap

Last updated: May 08,2024

Deprecated! Installation of this package may no longer be supported.

1. Install "python2-flask-jwt-extended" package

Learn how to install python2-flask-jwt-extended on openSUSE Leap


    
        
            $
        

        
            
                sudo zypper refresh
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo zypper install
            
                        
                python2-flask-jwt-extended
            
                    
    
    Copied

2. Uninstall "python2-flask-jwt-extended" package

This is a short guide on how to uninstall python2-flask-jwt-extended on openSUSE Leap:


    
        
            $
        

        
            
                sudo zypper remove
            
                        
                python2-flask-jwt-extended
            
                    
    
    Copied

3. Information about the python2-flask-jwt-extended package on openSUSE Leap

Information for package python2-flask-jwt-extended:
---------------------------------------------------
Repository : Main Repository
Name : python2-flask-jwt-extended
Version : 3.24.1-bp153.1.19
Arch : noarch
Vendor : openSUSE
Installed Size : 166,2 KiB
Installed : No
Status : not installed
Source package : python-flask-jwt-extended-3.24.1-bp153.1.19.src
Summary : A Flask extension that provides JWT support
Description :
Flask-JWT-Extended not only adds support for using JSON Web Tokens
(JWT) to Flask for protecting views, but also many
(optional) features built in to make working with JSON
Web Tokens easier. These include:
- Support for adding custom claims to JSON Web Tokens
- Custom claims validation on received tokens
- Creating tokens from complex objects or complex object from received tokens
- Refresh tokens
- Token freshness and separate view decorators to only allow fresh tokens
- Token revoking/blacklisting
- Storing tokens in cookies and CSRF protection