scope Alternatives - Go Authentication and OAuth

Popularity

1.4

Growing

Activity

0.0

Declining

Stars 10

Watchers 1

Forks 3

Last Commit about 1 year ago

Programming language: Go

License: MIT License

Tags: Authentication & OAuth

scope alternatives and similar packages

Based on the "Authentication and OAuth" category.
Alternatively, view scope alternatives based on common mentions on social networks and blogs.

scs

7.5 4.6 scope VS scs

Session Manager for HTTP servers.
paseto

6.6 0.5 scope VS paseto

Golang implementation of Platform-Agnostic Security Tokens (PASETO).

Get performance insights in less than 4 minutes

Scout APM uses tracing logic that ties bottlenecks to source code so you know the exact line of code causing performance issues and can get back to building a great product faster.

Sponsored scoutapm.com

jeff

5.5 0.6 scope VS jeff

Simple, flexible, secure and idiomatic web session management with pluggable backends.
go-guardian

5.3 0.0 scope VS go-guardian

Go-Guardian is a golang library that provides a simple, clean, and idiomatic way to create powerful modern API and web authentication that supports LDAP, Basic, Bearer token and Certificate based authentication.
branca

5.0 0.9 scope VS branca

Golang implementation of Branca Tokens.
sessionup

4.4 2.6 scope VS sessionup

Simple, yet effective HTTP session management and identification package.
sjwt

3.9 0.0 scope VS sjwt

Simple jwt generator and parser.
securecookie

3.3 2.6 scope VS securecookie

Efficient secure cookie encoding/decoding.
otpgo

1.8 7.1 scope VS otpgo

Time-Based One-Time Password (TOTP) and HMAC-Based One-Time Password (HOTP) library for Go.
signedvalue

1.3 0.0 scope VS signedvalue

Signed and timestamped strings compatible with Tornado's create_signed_value, decode_signed_value, and therefore set_secure_cookie and get_secure_cookie.
sessiongate-go

1.3 0.0 scope VS sessiongate-go

Go session management using the SessionGate Redis module.
go-email-normalizer

1.1 4.6 scope VS go-email-normalizer

Golang library for providing a canonical representation of email address.
cookiestxt

0.9 0.0 scope VS cookiestxt

provides parser of cookies.txt file format.

Do you think we are missing an alternative of scope or a related project?

Add another 'Authentication and OAuth' Package

Popular Comparisons

README

Scope

Easily Manage OAuth2 Scopes In Go

Scope Matching Using Wildcard Strategy

import "github.com/SonicRoshan/scope"

scopeA := "read:user:*"
scopeB := "read:user:username"

doesMatch := scope.MatchScopes(scopeA, scopeB)

This strategy will work like this :-

users.* matches users.read
users.* matches users.read.foo
users.read matches users.read
users does not match users.read
users.read.* does not match users.read
users.*.* does not match users.read
users.*.* matches users.read.own
users.*.* matches users.read.own.other
users.read.* matches users.read.own
users.read.* matches users.read.own.other
users.write.* does not match users.read.own
users.*.bar matches users.baz.bar
users.*.bar does not users.baz.baz.bar

Filtering Struct For Read Request

When a client request certain data, this function will eliminate any data in the struct for which the client does not have a read scope.

type user struct {
    username string `readScope:"user:read:username"`
    email string `readScope:"user:read:email"`
}


func main() {
    output := user{username : "Test", email : "[email protected]"}
    scopesHeldByClient := []string{"user:read:username"}
    scope.FilterRead(output, scopesHeldByClient)

    // Now output.email will be nil as client does not have scope required to read email field

    output := user{username : "Test", email : "[email protected]"}
    scopesHeldByClient := []string{"user:read:*"}
    scope.FilterRead(&output, scopesHeldByClient)

    // Now none of the field in output will be nil as client has scopes to read everything in user struct
}

scope

Easily Manage OAuth2 Scopes In Go.