sidebarItem belum fix

2025-05-28 07:23:47 +07:00
parent 692ffdf2f1
commit 453fccf550
14 changed files with 990 additions and 48 deletions
--- a/server/api/auth/[...].ts
+++ b/server/api/auth/[...].ts
@@ -0,0 +1,58 @@
+// import CredentialsProvider from 'next-auth/providers/credentials'
+import KeycloakProvider from 'next-auth/providers/keycloak'
+import { NuxtAuthHandler } from '#auth'
+console.log(KeycloakProvider)
+export default NuxtAuthHandler({
+  // TODO: SET A STRONG SECRET, SEE https://sidebase.io/nuxt-auth/configuration/nuxt-auth-handler#secret
+  secret: process.env.AUTH_SECRET || '32HslhZ8Hn97SsbxcmowhXvmNZ9cPGNE',
+  // TODO: ADD YOUR OWN AUTHENTICATION PROVIDER HERE, READ THE DOCS FOR MORE: https://sidebase.io/nuxt-auth
+  providers: [
+    // @ts-expect-error You need to use .default here for it to work during SSR. May be fixed via Vite at some point
+    KeycloakProvider.default({
+      clientId: process.env.KEYCLOAK_ID,
+      clientSecret: process.env.KEYCLOAK_SECRET,
+      issuer: process.env.KEYCLOAK_ISSUER,
+    }),
+    // // @ts-expect-error You need to use .default here for it to work during SSR. May be fixed via Vite at some point
+    // CredentialsProvider.default({
+    //   // The name to display on the sign in form (e.g. 'Sign in with...')
+    //   name: 'Credentials',
+    //   // The credentials is used to generate a suitable form on the sign in page.
+    //   // You can specify whatever fields you are expecting to be submitted.
+    //   // e.g. domain, username, password, 2FA token, etc.
+    //   // You can pass any HTML attribute to the <input> tag through the object.
+    //   credentials: {
+    //     username: { label: 'Username', type: 'text', placeholder: '(hint: jsmith)' },
+    //     password: { label: 'Password', type: 'password', placeholder: '(hint: hunter2)' }
+    //   },
+    //   authorize (credentials: any) {
+    //     console.warn('ATTENTION: You should replace this with your real providers or credential provider logic! The current setup is not safe')
+    //     // You need to provide your own logic here that takes the credentials
+    //     // submitted and returns either a object representing a user or value
+    //     // that is false/null if the credentials are invalid.
+    //     // NOTE: THE BELOW LOGIC IS NOT SAFE OR PROPER FOR AUTHENTICATION!
+
+    //     const user = { id: '1', name: 'J Smith', username: 'jsmith', password: 'hunter2' }
+
+    //     if (credentials?.username === user.username && credentials?.password === user.password) {
+    //       // Any object returned will be saved in `user` property of the JWT
+    //       return user
+    //     } else {
+    //       console.error('Warning: Malicious login attempt registered, bad credentials provided')
+
+    //       // If you return null then an error will be displayed advising the user to check their details.
+    //       return null
+
+    //       // You can also Reject this callback with an Error thus the user will be sent to the error page with the error message as a query parameter
+    //     }
+    //   }
+    // })
+  ],
+  pages: {
+    signIn: '/auth/login',
+    // signOut: '/auth/signOut',
+    // error: '/auth/error',
+    // verifyRequest: '/auth/verify-request',
+    // newUser: '/auth/new-user'
+  },
+})