सार्वजनिक जानकारी से बना चयन मार्गदर्शन। केवल संदर्भ हेतु।
Keycloak Flutter एक क्लाइंट एडेप्टर है जो फ्लटर एप्लिकेशन के लिए उपलब्ध है, जो Keycloak से एकीकरण की अनुमति देता है, एक ओपन-सोर्स पहचान और एक्सेस मैनेजमेंट सॉल्यूशन। keycloak-js के आधार पर, यह फ्लटर ऐप्स के लिए प्रमाणीकरण और अधिकार प्रदान करता है, जिसमें लॉगिन, लॉगआउट, टोकन प्रबंधन और भूमिका-आधारित एक्सेस कंट्रोल जैसी सुविधाएं शामिल हैं। इस पैकेज के माध्यम से यह यूजर के सुरक्षित प्रमाणीकरण को मोबाइल और वेब वातावरण में सरल बनाता है, जिसमें Keycloak की मजबूत सुरक्षा फ्रेमवर्क का उपयोग किया जाता है।
उपयोग
Flutter ऐप्स में सुरक्षित उपयोगकर्ता प्रमाणीकरण
मौजूदा Keycloak सर्वर के साथ एकीकरण
मोबाइल ऐप्स में भूमिका-आधारित पहुंच नियंत्रण
कई सेवाओं के माध्यम से एकल साइन-ऑन (SSO)
हाइब्रिड एप्लिकेशन में उपयोगकर्ता सत्र का प्रबंधन
मुख्य विशेषताएँ
Keycloak सर्वर के माध्यम से प्रमाणीकरण
टोकन रिफ्रेश और स्टोरेज
SSO के लिए समर्थन
भूमिका और अनुमति जाँच
हल्का और keycloak-js के साथ सुसंगत
इनके लिए उपयुक्त
सुरक्षित लॉगिन की आवश्यकता वाले मोबाइल ऐप्स
Keycloak का उपयोग करने वाले एंटरप्राइज एप्लिकेशन
SSO एकीकरण की आवश्यकता वाले ऐप्स
Keycloak के परिचित विकासकर्ता
पहचान प्रबंधन पर बल देने वाले प्रोजेक्ट
विचार योग्य बातें
एक चल रहे Keycloak सर्वर की आवश्यकता है
सीमित प्लेटफॉर्म समर्थन (कोई स्पष्ट प्लेटफॉर्म नहीं बताए गए)
सही Keycloak कॉन्फ़िगरेशन पर निर्भर करता है
कोई बिल्ट-इन UI कंपोनेंट नहीं
टोकन समाप्ति और पुनर्नवीनीकरण का हस्तचालित निर्माण
मूल README
संबंधित सोर्स रिपॉज़िटरी के मूल README का स्नैपशॉट। नवीनतम सामग्री के लिए रिपॉज़िटरी देखें।
Keycloak Flutter
Easy Keycloak setup for Flutter applications.
About
This library helps you to
use keycloak-js in Flutter
applications providing the following features:
A Keycloak Service which wraps the keycloak-js methods to be used in Flutter, giving extra
functionalities to the original functions and adding new methods to make it easier to be consumed by
Flutter applications.
Generic AuthGuard implementation, so you can customize your own AuthGuard logic inheriting the authentication
logic and the roles load. (coming soon)
A HttpClient interceptor that adds the authorization header to all HttpClient requests.It is also possible to disable this interceptor or exclude routes from having the authorization header. (coming
soon)
This documentation also assists you to configure the keycloak in your Flutter applications and with
the client setup in the admin console of your keycloak installation. (coming soon)
Compatibility
The table below shows the compatibility of keycloak flutter with keycloak. Note that this table will be updated and is
not set in stone
Keycloak_flutter version
Keycloak version
v0.0.3
v10 - v13
v0.0.19
v17 - v19
v0.0.20 - latest
v20 - latest
Installation
Firstly, you need to have keycloak configured. Duh!
Include keycloak_flutter as a dependency in the
dependencies section of your pubspec.yaml file :
Next, In your web/index.html, you need to add a script with a source that references your keycloak.js file. You can
find v10.0.2 in the example project. Your head tag should look as below.
<!DOCTYPE html><html><head><basehref="/"><!-- CODE REMOVED FOR BREVITY --><linkrel="manifest"href="manifest.json"><scriptsrc="js/keycloak.js"></script></head><body><script>if ('serviceWorker'in navigator) {
window.addEventListener('flutter-first-frame', function () {
navigator.serviceWorker.register('flutter_service_worker.js');
});
}
</script><scriptsrc="main.dart.js"type="application/javascript"></script></body></html>
Now, create a frontend client as you usually would in keycloak. Ensure you set your web origins configuration properly.
If you are still having issues, you can import the client included in the
example application
Choosing the right keycloak-js version
The Keycloak client documentation recommends to use the same version of your Keycloak installation.
A best practice is to load the JavaScript adapter directly from Keycloak Server as it will automatically be updated
when you upgrade the server. If you copy the adapter to your web application instead, make sure you upgrade the
adapter
only after you have upgraded the server.
You can now use keycloak in your app.
Note
You need to ensure you do not create multiple instances of keycloak. The example below uses a provider to ensure this.
Use the code provided below as an example and implement it's functionality in your application. In this process ensure
that the configuration you are providing matches that of your client as configured in Keycloak.
Please check and run the example code included in this repository.
A sample keycloak client is also included in the example codebase
lateKeycloakService keycloakService;
voidmain() async {
keycloakService = KeycloakService(KeycloakConfig(
url: 'http://localhost:8080', // Keycloak auth base url
realm: 'sample',
clientId: 'sample-flutter'));
keycloakService.init(
initOptions: KeycloakInitOptions(
onLoad: 'check-sso',
responseMode: 'query',
silentCheckSsoRedirectUri:
'${window.location.origin}/silent-check-sso.html',
),
);
runApp(MyApp());
}
classMyAppextendsStatelessWidget{
// This widget is the root of your application.@overrideWidgetbuild(BuildContext context) {
returnMaterialApp.router(
title: 'Keycloak Demo',
debugShowCheckedModeBanner: false,
theme: ThemeData(
primarySwatch: Colors.blue,
),
routerConfig: _router,
);
}
}
classMyHomePageextendsStatefulWidget{
MyHomePage({Key? key, this.title}) : super(key: key);
finalString? title;
@override_MyHomePageStatecreateState() => _MyHomePageState();
}
class_MyHomePageStateextendsState<MyHomePage> {
KeycloakProfile? _keycloakProfile;
void_login() {
keycloakService.login(KeycloakLoginOptions(
redirectUri: '${window.location.origin}',
));
}
@overridevoidinitState() {
// TODO: implement initStatesuper.initState();
try {
WidgetsBinding.instance.addPostFrameCallback((timeStamp) async {
keycloakService.keycloakEventsStream.listen((event) async {
print(event);
if (event.type == KeycloakEventType.onAuthSuccess) {
_keycloakProfile = await keycloakService.loadUserProfile();
} else {
_keycloakProfile = null;
}
setState(() {});
});
if (keycloakService.authenticated) {
_keycloakProfile = await keycloakService.loadUserProfile(false);
}
setState(() {});
});
} catch (e) {
print(e);
}
}
@overrideWidgetbuild(BuildContext context) {
// This method is rerun every time setState is called, for instance as done// by the _incrementCounter method above.//// The Flutter framework has been optimized to make rerunning build methods// fast, so that you can just rebuild anything that needs updating rather// than having to individually change instances of widgets.returnScaffold(
appBar: AppBar(
// Here we take the value from the MyHomePage object that was created by// the App.build method, and use it to set our appbar title.
title: Text('Sample'),
actions: [
IconButton(
icon: Icon(Icons.logout),
onPressed: () async {
await keycloakService.logout();
}),
],
),
body: Center(
child: Column(
mainAxisAlignment: MainAxisAlignment.center,
children: <Widget>[
Text(
'Welcome ${_keycloakProfile?.username ?? 'Guest'}',
style: Theme
.of(context)
.textTheme
.headline4,
),
SizedBox(
height: 20,
),
if (_keycloakProfile?.username == null)
ElevatedButton(
onPressed: _login,
child: Text(
'Login',
style: Theme
.of(context)
.textTheme
.headline4,
),
),
SizedBox(
height: 20,
),
if (_keycloakProfile?.username != null)
ElevatedButton(
onPressed: () async {
print('refreshing token');
await keycloakService.updateToken(1000).then((value) {
print(value);
}).catchError((onError) {
print(onError);
});
},
child: Text(
'Refresh token',
style: Theme
.of(context)
.textTheme
.headline4,
),
),
],
),
),
floatingActionButton: FloatingActionButton(
onPressed: _login,
tooltip: 'Login',
child: Icon(Icons.login),
), // This trailing comma makes auto-formatting nicer for build methods.
);
}
}
final _router = GoRouter(
routes: [
GoRoute(
path: '/',
builder: (context, state) => MyHomePage(),
),
],
);
In the example we have set up Keycloak to use a silent check-sso. With this feature enabled, your browser will not do
a full redirect to the Keycloak server and back to your application, instead this action will be performed in a hidden
iframe, so your application resources only need to be loaded and parsed once by the browser when the app is initialized
and not again after the redirect back from Keycloak to your app.
To ensure that Keycloak can communicate through the iframe you will have to serve a static HTML asset from your
application at the location provided in silentCheckSsoRedirectUri.
Create a file called silent-check-sso.html in the assets directory of your application and paste in the contents as
seen below.
Please check the example code included in this repository
If you want to know more about these options and various other capabilities of the Keycloak client is recommended to
read the JavaScript Adapter documentation.
FAQ
Q: Why am I getting 'Promise was rejected with a value of undefined'?
A: Ensure you have setup your frontend client properly, specifically the web origins configuration. This issue usually
occurs when the login status iframe cannot check for the login status of the user because of wrong web origins config.
Please check the included client in the example app.
Q: Do I have to use go_router like the example app??
A: No. You absolutely do not. However, you need to use a router that supports and recognises url query parameters or url
fragments because this is how keycloak communicates the login state of your application. Below are some that will work.