-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
iOS ownCloud signin framework #59
Comments
Nodding. I could do that. It seems typical, however, for systems to provide a sign-in library that has a similar look and feel to the native look and feel so users feel more comfortable. E.g. With Google Sign in (for Google Drive) or with Dropbox. It seemed like a good way to do that was to use the same code as for ownCloud. Beating on this more this morning, and being more selective about the files I'm including I finally have a clean build. |
Well, I agree now. After beating on this some more, there are a large number of dependencies (e.g., for logging) that I just don't want to deal with. I'm trying AppAuth, and made a little progress, but am faltering at the discovery step. It's trying to use a path |
ownCloud server speaks only OAuth 2.0, no OpenID connect. This will help you: |
Hi,
I have a need in my own project to embed ownCloud sign in as an optional build element. In my case as a Cocoapod subspec. So, I want to create an ownCloud sign in framework as a Cocoapod. I'm part way into doing this -- it appears to require embedding ownCloudSDK, ownCloudUI and large parts of the ownCloud iOS app code into a framework (e.g., because I'd like to use the BookmarksViewController). Progressing on this, I've reached a stumbling block because of the use in the ownCloud iOS app of an internal framework-- ownCloudApp. I guess I could try to split that off and build it as it's own framework. I can't easily pull out the ownCloudApp framework because its very difficult for me to get the ownCloud iOS app to build. Just thought I'd check in here for ideas. Thoughts?
Thanks!
Chris.
The text was updated successfully, but these errors were encountered: