exvo-auth 0.7.7 → 0.7.8
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- data/README +6 -7
- data/VERSION +1 -1
- data/exvo-auth.gemspec +1 -1
- metadata +2 -2
data/README
CHANGED
@@ -98,17 +98,16 @@ Inter-Application Communication
|
|
98
98
|
consumer = ExvoAuth::Autonomous::Consumer.new(
|
99
99
|
:provider_id => "this is client_id of the app you want to connect to"
|
100
100
|
)
|
101
|
-
consumer.
|
101
|
+
consumer.get(*args) - interface is exactly the same like in HTTParty. All http methods are available (post, put, delete, head, options).
|
102
102
|
|
103
103
|
|
104
104
|
# Provider side
|
105
105
|
|
106
|
-
|
107
|
-
:consumer_id => "the client_id of the consuming app",
|
108
|
-
:access_token => "the access_token of the consuming app"
|
109
|
-
)
|
110
|
-
provider.scopes => ["users", "payments"] # example access scopes defined in auth server.
|
111
|
-
|
106
|
+
See #authenticate_app_in_scope!(scope) method in ExvoAuth::Controllers::Rails (or Merb). This method lets you create a before filter.
|
112
107
|
Scopes are used by providing app to check if a given consuming app should have access to a given resource inside a scope.
|
113
108
|
If scopes are empty, then provider app should not present any resources to consumer.
|
114
109
|
|
110
|
+
# Example of the before filter for provider controller:
|
111
|
+
|
112
|
+
before_filter {|c| c.authenticate_app_in_scope!("payments") }
|
113
|
+
|
data/VERSION
CHANGED
@@ -1 +1 @@
|
|
1
|
-
0.7.
|
1
|
+
0.7.8
|
data/exvo-auth.gemspec
CHANGED